You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
server self hosted on Home Assistant OS on my Raspbery pi, using Home Assistant Add-on Current version: 24.12.0-alpine
client access from Windows Application from my Windows 10 machine in same local network
stable version
How can we reproduce the issue?
Side panel > More > Payees > click "Create rule" of any one of the payee
change condition match from "payee" to "imported payee"
change condition to "contains"
Error would pop up here. seems to mess up the whole system so I need to restart the server
the same error seems not pop up if I go to More > Rules and do the same thing. so it only happens from payee?
Where are you hosting Actual?
Other
What browsers are you seeing the problem on?
Desktop App (Electron)
Operating System
Windows 10
The text was updated successfully, but these errors were encountered:
Server Log: conditionsToAQL: invalid condition: RuleError: contains must have non-empty string (field: imported_payee)
VM354:2 Server Log: [Exception] TypeError: Cannot read properties of null (reading 'op')
at gT (/Applications/Actual.app/Contents/Resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:193:1004)
at Array.map (<anonymous>)
at gO (/Applications/Actual.app/Contents/Resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:193:1504)
at b5.make-filters-from-conditions (/Applications/Actual.app/Contents/Resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:294:1147)
at oY (/Applications/Actual.app/Contents/Resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:62:2551)
at ParentPort.<anonymous> (/Applications/Actual.app/Contents/Resources/app.asar/build/loot-core/lib-dist/electron/bundle.desktop.js:62:3194)
at ParentPort.emit (node:events:518:28)
at ParentPort.i.emit (node:electron/js2c/utility_init:2:15723)
And then a restart is required to get things back to normal. Just refreshing the page is insufficient - it gets stuck on "Loading global preferences".
A workaround is to first select "imported payee one of", provide a value, and then select "contains". This will ensure the contains value isn't empty, which is what triggers the error.
Verified issue does not already exist?
What happened?
My environment:
How can we reproduce the issue?
Side panel > More > Payees > click "Create rule" of any one of the payee
change condition match from "payee" to "imported payee"
change condition to "contains"
Error would pop up here. seems to mess up the whole system so I need to restart the server
the same error seems not pop up if I go to More > Rules and do the same thing. so it only happens from payee?
Where are you hosting Actual?
Other
What browsers are you seeing the problem on?
Desktop App (Electron)
Operating System
Windows 10
The text was updated successfully, but these errors were encountered: