github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Cannot open account after upgrading to v24.12.0 from v24.8.0 #1733

New Issue
Closed
opened 2026-02-28 19:53:21 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-02-28 19:53:21 -06:00
Owner
Copy Link

Originally created by @DracoC77 on GitHub (Jan 2, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I attempted to import a QFX file from Chase credit cards into the wrong account, realized I was loading the QFX file into the wrong account and clicked cancel. Now anytime I try to navigate to my chase account (not the one I had open when I mistakenly tried to import the QFX file), it sends me to a fatal error screen with the following errors:

Note that I CAN get to the other accounts just fine, just when I click on that specific account it errors out:

"Fatal Error
There was an unrecoverable error in the UI. Sorry!"

TypeError: Cannot read properties of null (reading 'num1') at IC (https://--redacted--/static/js/index.JHeog5K2.js:98:43758) at https://--redacted--/static/js/index.JHeog5K2.js:98:123249 at Array.map () at https://--redacted--/static/js/index.JHeog5K2.js:98:123180 at Object.cM [as useMemo] (https://--redacted--/static/js/index.JHeog5K2.js:57:23922) at Ye.useMemo (https://--redacted--/static/js/index.JHeog5K2.js:10:6208) at yRe (https://--redacted--/static/js/index.JHeog5K2.js:98:123141) at v (https://--redacted--/static/js/useAccountPreviewTransactions.EORsFDeG.chunk.js:1:117) at Jo (https://--redacted--/static/js/wide.k1vKSsoJ.chunk.js:1:89660) at kk (https://--redacted--/static/js/index.JHeog5K2.js:57:19539)

How can we reproduce the issue?

Unclear root cause, UI fatal error each time I go to account

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 10

Originally created by @DracoC77 on GitHub (Jan 2, 2025). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I attempted to import a QFX file from Chase credit cards into the wrong account, realized I was loading the QFX file into the wrong account and clicked cancel. Now anytime I try to navigate to my chase account (not the one I had open when I mistakenly tried to import the QFX file), it sends me to a fatal error screen with the following errors: Note that I CAN get to the other accounts just fine, just when I click on that specific account it errors out: "Fatal Error There was an unrecoverable error in the UI. Sorry!" TypeError: Cannot read properties of null (reading 'num1') at IC (https://--redacted--/static/js/index.JHeog5K2.js:98:43758) at https://--redacted--/static/js/index.JHeog5K2.js:98:123249 at Array.map (<anonymous>) at https://--redacted--/static/js/index.JHeog5K2.js:98:123180 at Object.cM [as useMemo] (https://--redacted--/static/js/index.JHeog5K2.js:57:23922) at Ye.useMemo (https://--redacted--/static/js/index.JHeog5K2.js:10:6208) at yRe (https://--redacted--/static/js/index.JHeog5K2.js:98:123141) at v (https://--redacted--/static/js/useAccountPreviewTransactions.EORsFDeG.chunk.js:1:117) at Jo (https://--redacted--/static/js/wide.k1vKSsoJ.chunk.js:1:89660) at kk (https://--redacted--/static/js/index.JHeog5K2.js:57:19539) ### How can we reproduce the issue? Unclear root cause, UI fatal error each time I go to account ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 10
GiteaMirror added the bug label 2026-02-28 19:53:21 -06:00
GiteaMirror commented 2026-02-28 19:53:22 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 2, 2025):

Looks like the db has bad values. Do you have a backup? That would be the easiest fix

@youngcw commented on GitHub (Jan 2, 2025): Looks like the db has bad values. Do you have a backup? That would be the easiest fix
GiteaMirror commented 2026-02-28 19:53:22 -06:00
Author
Owner
Copy Link

@DracoC77 commented on GitHub (Jan 2, 2025):

I just tried an older image snapshot of my whole server and took a backup file from that (previously on v24.8.0), imported into v24.12.0 and looks like the problem happened when I went from v24.8.0 to v24.12.0...

In the dashboard after the update I can see a different summary balance for the troubled account, but when I go into the account it gives me the same error messages... so there's something interacting between my database for that account and v24.12.0 specifically.

[FIXED] Also trying to go back docker version to v24.8.0 gives me "Rejection: Error: Missing migration file: 1718889148000-openid.js" error when I try to start the docker container... even after I deleted all directories AND docker images (weird). [FIXED... I missed a .migrate file in the actual-data folder, doh!]

@DracoC77 commented on GitHub (Jan 2, 2025): I just tried an older image snapshot of my whole server and took a backup file from that (previously on v24.8.0), imported into v24.12.0 and looks like the problem happened when I went from v24.8.0 to v24.12.0... In the dashboard after the update I can see a different summary balance for the troubled account, but when I go into the account it gives me the same error messages... so there's something interacting between my database for that account and v24.12.0 specifically. [FIXED] Also trying to go back docker version to v24.8.0 gives me "Rejection: Error: Missing migration file: 1718889148000-openid.js" error when I try to start the docker container... even after I deleted all directories AND docker images (weird). [FIXED... I missed a .migrate file in the actual-data folder, doh!]
GiteaMirror commented 2026-02-28 19:53:22 -06:00
Author
Owner
Copy Link

@DracoC77 commented on GitHub (Jan 2, 2025):

Ok was able to downgrade my actual-server to v24.8.0, my backup file from the same time-frame (v24.8.0) works just fine on the troubled account when running v24.8.0 actual-server.

When I try to load the latest backup file (recently upgraded/migrated from v24.8.0 to v24.12.0 in server upgrade) into v24.8.0 actual-server, the troubled account still gives me the same fatal error message.

Is it possible/worth trying to inspect the sqlite database files directly to look for the error? Any guidance on what to look for?

@DracoC77 commented on GitHub (Jan 2, 2025): Ok was able to downgrade my actual-server to v24.8.0, my backup file from the same time-frame (v24.8.0) works just fine on the troubled account when running v24.8.0 actual-server. When I try to load the latest backup file (recently upgraded/migrated from v24.8.0 to v24.12.0 in server upgrade) into v24.8.0 actual-server, the troubled account still gives me the same fatal error message. Is it possible/worth trying to inspect the sqlite database files directly to look for the error? Any guidance on what to look for?
GiteaMirror commented 2026-02-28 19:53:22 -06:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jan 2, 2025):

Can you reproduce on https://edge.actualbudget.org? The trace looks awfully familiar from the schedules bug

@matt-fidd commented on GitHub (Jan 2, 2025): Can you reproduce on https://edge.actualbudget.org? The trace looks awfully familiar from the schedules bug
GiteaMirror commented 2026-02-28 19:53:23 -06:00
Author
Owner
Copy Link

@DracoC77 commented on GitHub (Jan 3, 2025):

Just spun up a new local instance of edge docker image and the trouble account seems to be working now. Will re-confirm on my "prod" setup before closing the bug

@DracoC77 commented on GitHub (Jan 3, 2025): Just spun up a new local instance of edge docker image and the trouble account seems to be working now. Will re-confirm on my "prod" setup before closing the bug
GiteaMirror commented 2026-02-28 19:53:23 -06:00
Author
Owner
Copy Link

@DracoC77 commented on GitHub (Jan 3, 2025):

Confirmed that latest edge build seems to fix this problem with the "corrupted" database. Trouble account now loads normally without a fatal error. Based on the error codes likely a dupliciate of 4062

@DracoC77 commented on GitHub (Jan 3, 2025): Confirmed that latest edge build seems to fix this problem with the "corrupted" database. Trouble account now loads normally without a fatal error. Based on the error codes likely a dupliciate of [4062](https://github.com/actualbudget/actual/issues/4062)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1733
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?