Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 task done
DracoC77 opened this issue Jan 2, 2025 · 6 comments
Closed
1 task done
Labels
bug Something isn't working

Comments

@DracoC77
Copy link

DracoC77 commented 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

@DracoC77 DracoC77 added the bug Something isn't working label Jan 2, 2025
@youngcw
Copy link
Member

youngcw commented Jan 2, 2025

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

@DracoC77
Copy link
Author

DracoC77 commented 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 DracoC77 changed the title [Bug]: Cannot open account after QFX import [Bug]: Cannot open account after upgrading to v24.12.0 from v24.8.0 Jan 2, 2025
@DracoC77
Copy link
Author

DracoC77 commented 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?

@matt-fidd
Copy link
Contributor

matt-fidd commented Jan 2, 2025

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

@DracoC77
Copy link
Author

DracoC77 commented 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
Copy link
Author

DracoC77 commented 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 DracoC77 closed this as completed Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants