mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
[GH-ISSUE #5151] [Bug]: restablishing sync for one of my accounts causes error #91826
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#91826
Reference in New Issue
Block a user
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?
Originally created by @glenndegroote on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5151
Verified issue does not already exist?
What happened?
the sync with one of my accounts was expired. i reastablished the sync via gocardless, went through the process and even received confirmation from my fintro app that the authorisation was granted. Immediatly i received an issue that the changes could not be synced and i should log an issue through github
How can we reproduce the issue?
the sync with one of my accounts was expired. i reastablished the sync via gocardless, went through the process and even received confirmation from my fintro app that the authorisation was granted. Immediatly i received an issue that the changes could not be synced and i should log an issue through github
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Chrome
Operating System
Windows 11
@matt-fidd commented on GitHub (Jun 13, 2025):
Please could you provide the logs from your browser console (https://balsamiq.com/support/faqs/browserconsole/)? Hopefully something in there should explain what has gone wrong.
@glenndegroote commented on GitHub (Jun 13, 2025):
Hi Matt,
Please find herewith the logs and a screenshot of the sync issue which immediately appears after the gocardless screen automatically closes so even right before make the connection with the appropriate account.
[cid:e2e9e11c-840d-49d3-8d96-095f512959ee]
kr
Glenn
From: Matt Fiddaman @.>
Sent: Friday, June 13, 2025 1:48 PM
To: actualbudget/actual @.>
Cc: glenndegroote @.>; Author @.>
Subject: Re: [actualbudget/actual] [Bug]: restablishing sync for one of my accounts causes error (Issue #5151)
[https://avatars.githubusercontent.com/u/81489167?s=20&v=4]matt-fidd left a comment (actualbudget/actual#5151)https://github.com/actualbudget/actual/issues/5151#issuecomment-2970145472
Please could you provide the logs from your browser console (https://balsamiq.com/support/faqs/browserconsole/)? Hopefully something in there should explain what has gone wrong.
—
Reply to this email directly, view it on GitHubhttps://github.com/actualbudget/actual/issues/5151#issuecomment-2970145472, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BTQ6ZU5TUD7RLZSX4CYT3AD3DK3BFAVCNFSM6AAAAAB7HL4NC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZQGE2DKNBXGI.
You are receiving this because you authored the thread.
index.ts:113 Backend: Trying to connect to client
index.ts:49 Backend: Client connected
Reading meta...
Got meta for documents-Actual-My-Finances-f022634-db.sqlite: undefined
913674da-91ca-49b5-859a-38308ca6650c:1 Reading meta...
913674da-91ca-49b5-859a-38308ca6650c:1 Got meta for documents-Actual-My-Finances-f022634-db.sqlite: Object
sql-wasm.js:119 Opened!
sheet.ts:166 Loading fresh spreadsheet
index.ts:3 Syncing since 2025-06-13T12:15:49.219Z-0000-0000000000000000 0 (attempt: 0)
index.ts:3 Got messages from server 0
index.ts:3 Syncing since 1970-01-01T00:00:00.000Z-0000-0000000000000000 0 (attempt: 1)
index.ts:3 Got messages from server 115853
index.ts:3 Syncing since 2025-06-13T12:21:14.161Z-1AB2-b76d9ee8dc17bcfa 0 (attempt: 0)
index.ts:3 Got messages from server 0
index.ts:3 Syncing since 2025-06-13T12:21:14.161Z-1AB2-b76d9ee8dc17bcfa 0 (attempt: 0)
index.ts:3 Got messages from server 0
sql-wasm.js:119 Opened!
sql-wasm.js:119 Opened!
index.ts:3 Syncing since 2025-06-13T12:21:14.161Z-1AB2-b76d9ee8dc17bcfa 0 (attempt: 0)
index.ts:3 Got messages from server 0
index.web.ts:88 SELECT timestamp, dataset, row, column, value FROM messages_crdt WHERE timestamp > ?
index.ts:563 Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
index.ts:2 [Exception] Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
captureException @ index.ts:2
sync-events.ts:357 unknown error Object
(anonymous) @ sync-events.ts:357
yae @ index.browser.ts:70
e.onmessage @ index.browser.ts:137
index.web.ts:88 SELECT id, bank_id FROM banks WHERE bank_id = ?
index.ts:2 [Exception] Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at first (index.ts:173:21)
at findOrCreateBank (link.ts:7:22)
at linkGoCardlessAccount (app.ts:128:22)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
captureException @ index.ts:2
sql-wasm.js:89 Uncaught (in promise) Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at first (index.ts:173:21)
at findOrCreateBank (link.ts:7:22)
at linkGoCardlessAccount (app.ts:128:22)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
index.web.ts:88 SELECT timestamp, dataset, row, column, value FROM messages_crdt WHERE timestamp > ?
index.ts:563 Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
index.ts:2 [Exception] Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
captureException @ index.ts:2
sync-events.ts:357 unknown error Object
(anonymous) @ sync-events.ts:357
yae @ index.browser.ts:70
e.onmessage @ index.browser.ts:137
index.web.ts:88 SELECT timestamp, dataset, row, column, value FROM messages_crdt WHERE timestamp > ?
index.ts:563 Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
index.ts:2 [Exception] Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
captureException @ index.ts:2
sync-events.ts:357 unknown error Object
(anonymous) @ sync-events.ts:357
yae @ index.browser.ts:70
e.onmessage @ index.browser.ts:137
index.web.ts:88 SELECT timestamp, dataset, row, column, value FROM messages_crdt WHERE timestamp > ?
index.ts:563 Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
index.ts:2 [Exception] Error: database disk image is malformed
at c.handleError (sql-wasm.js:89:129)
at a.step (sql-wasm.js:80:69)
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9
captureException @ index.ts:2
sync-events.ts:357 unknown error Object
(anonymous) @ sync-events.ts:357
yae @ index.browser.ts:70
e.onmessage @ index.browser.ts:137
@Martin-Fox commented on GitHub (Jun 17, 2025):
For me, when I try to link any account (or create a new one linked), I have this error:
An error occurred while linking your account, sorry! The potential issue could be: Request failed with status code 404@matt-lethargic commented on GitHub (Jun 17, 2025):
Looking at the logs for my Docker instance of Actual I'm seeing that a call is being made to this url
https://bankaccountdata.gocardless.com/api/v2/requisitions/undefined/a 404 is being returned, maybe because of the "undefined" segment??Trying to get a better view of my logs to get more infor
@Martin-Fox commented on GitHub (Jun 18, 2025):
@matt-lethargic the same in my case.
I just don't know if problem is on actual or gocardless :/
@matt-lethargic commented on GitHub (Jun 18, 2025):
I'd suggest that it's Actual's issue as it's sending a request to
https://bankaccountdata.gocardless.com/api/v2/requisitions/undefined/and GoCardless' documentation says that the word "undefined" should be the requisition id. I'm not a JS dev, but I do know that undefined is a JS thing.@Martin-Fox commented on GitHub (Jun 18, 2025):
I hope this can be fixed, as I cannot use actual budget without sync 🥹
@glenndegroote commented on GitHub (Jun 18, 2025):
Hi
I fear Martins problem has nothing to do with the issue i reported.
@matt-lethargic were you able to check the logs i shared?
Thanks for your help!
Kr
Glenn
@Martin-Fox commented on GitHub (Jun 18, 2025):
I'm not sure, but I also have this "undefined" in logs
@matt-fidd commented on GitHub (Jun 18, 2025):
This sounds the same as https://github.com/actualbudget/actual/issues/5152 which is fixed in the nightly (edge) builds by https://github.com/actualbudget/actual/pull/5150. Could you try swapping to the docker edge tag and seeing if the problem is resolved?
@Martin-Fox commented on GitHub (Jun 18, 2025):
@matt-fidd yes !!
On the edge it's working
@matt-fidd commented on GitHub (Jun 18, 2025):
Great! I'll close this off now then - this fix will be included in the next stable release.
@glenndegroote commented on GitHub (Jun 19, 2025):
This is great! Good that Martin's problem got resolved. I just tried again, my issue is unfortunatly still there.
What to do next?
index.ts:2 [Exception] Error: database disk image is malformed
at runQuery (index.web.ts:77:19)
at db_runQuery (index.ts:129:12)
at _fullSync (index.ts:491:10)
at index.ts:561:22
at async.ts:68:20
at app_sync (app.ts:20:16)
at runHandler (mutators.ts:67:19)
at index.ts:57:9