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

[Bug]: Unable to open file after latest Actual upgrade #2778

New Issue
Closed
opened 2026-02-28 20:27:35 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-02-28 20:27:35 -06:00
Owner
Copy Link

Originally created by @xonev on GitHub (Jan 6, 2026).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am using Actual on PikaPods.

I opened my "My Finances" file on my phone, and I was prompted to reload and upgrade to the latest version of Actual. I did so. Immediately after I did so, I received an error popup:

We had an unknown problem opening "My-Finances-6ac7293".

And now I cannot open that file on my phone or on my computer. Looking at the dev console on my computer I see error messages like the following:

Error updating budget Error: UNIQUE constraint failed: preferences.id
    at c.handleError (sql-wasm.js:89:129)
    at a.step (sql-wasm.js:80:69)
    at c.exec (sql-wasm.js:86:486)
    at execQuery$2 (index.web.ts:105:6)
    at migrations.ts:121:11
    at applyMigration (migrations.ts:137:11)
    at async migrate (migrations.ts:171:27)
    at async update.ts:10:1
    at async updateVersion (update.ts:34:23)
    at async _loadBudget (app.ts:544:7)

My other budget file "Oxley Ventures LLC" opens without issue.

Image

How can we reproduce the issue?

I don't know how to reproduce it, unfortunately. My best hunch is that it's an issue migrating a file with end-to-end encryption?

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Chrome

Operating System

Mac OSX

Originally created by @xonev on GitHub (Jan 6, 2026). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I am using Actual on PikaPods. I opened my "My Finances" file on my phone, and I was prompted to reload and upgrade to the latest version of Actual. I did so. Immediately after I did so, I received an error popup: ``` We had an unknown problem opening "My-Finances-6ac7293". ``` And now I cannot open that file on my phone or on my computer. Looking at the dev console on my computer I see error messages like the following: ``` Error updating budget Error: UNIQUE constraint failed: preferences.id at c.handleError (sql-wasm.js:89:129) at a.step (sql-wasm.js:80:69) at c.exec (sql-wasm.js:86:486) at execQuery$2 (index.web.ts:105:6) at migrations.ts:121:11 at applyMigration (migrations.ts:137:11) at async migrate (migrations.ts:171:27) at async update.ts:10:1 at async updateVersion (update.ts:34:23) at async _loadBudget (app.ts:544:7) ``` My other budget file "Oxley Ventures LLC" opens without issue. <img width="1711" height="1032" alt="Image" src="https://github.com/user-attachments/assets/c499f15f-1973-4d0a-95c8-224e0a7419dd" /> ### How can we reproduce the issue? I don't know how to reproduce it, unfortunately. My best hunch is that it's an issue migrating a file with end-to-end encryption? ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Chrome ### Operating System Mac OSX
GiteaMirror added the bugneeds info labels 2026-02-28 20:27:35 -06:00
GiteaMirror commented 2026-02-28 20:27:36 -06:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Jan 8, 2026):

@xonev Are you still experiencing this issue? Would you be able to provide the export of the budget file in question so we can troubleshoot?

@joel-jeremy commented on GitHub (Jan 8, 2026): @xonev Are you still experiencing this issue? Would you be able to provide the export of the budget file in question so we can troubleshoot?
GiteaMirror commented 2026-02-28 20:27:36 -06:00
Author
Owner
Copy Link

@xonev commented on GitHub (Jan 8, 2026):

@joel-jeremy yes, I'm still experiencing it. Oddly, one of my computers is still able to access the file, but I can't access it on my other computer or on my phone.
I was able to export the file on the computer that works. I can upload that version of the file, but I wonder if it will still exhibit the problem.

@xonev commented on GitHub (Jan 8, 2026): @joel-jeremy yes, I'm still experiencing it. Oddly, one of my computers is still able to access the file, but I can't access it on my other computer or on my phone. I was able to export the file on the computer that works. I can upload that version of the file, but I wonder if it will still exhibit the problem.
GiteaMirror commented 2026-02-28 20:27:37 -06:00
Author
Owner
Copy Link

@xonev commented on GitHub (Jan 8, 2026):

@joel-jeremy the fact that it was working on one of my computers made me suspicious that somehow the data on my other computer was corrupted. I cleared site data on the other computer and reloaded and everything works now... So I think there was some local data corruption or something.

@xonev commented on GitHub (Jan 8, 2026): @joel-jeremy the fact that it was working on one of my computers made me suspicious that somehow the data on my other computer was corrupted. I cleared site data on the other computer and reloaded and everything works now... So I think there was some local data corruption or something.
GiteaMirror commented 2026-02-28 20:27:38 -06:00
Author
Owner
Copy Link

@kimneu commented on GitHub (Jan 13, 2026):

I had the exact same problem on PikaPods with v26.1.0.

SOLUTION: Clearing the browser's website data fixed it for me!

  • Chrome: Settings → Privacy → Site Settings → View permissions and data stored across sites → Search for your Actual URL → Clear data
  • Firefox: Right-click in address bar → Page Info → Permissions → Clear Cookies and Site Data

Ctrl+Shift+R (hard reload) was NOT enough - you need to clear LocalStorage/IndexedDB.

After clearing and reloading, the budget opened without issues.

@kimneu commented on GitHub (Jan 13, 2026): I had the exact same problem on PikaPods with v26.1.0. SOLUTION: Clearing the browser's website data fixed it for me! - Chrome: Settings → Privacy → Site Settings → View permissions and data stored across sites → Search for your Actual URL → Clear data - Firefox: Right-click in address bar → Page Info → Permissions → Clear Cookies and Site Data Ctrl+Shift+R (hard reload) was NOT enough - you need to clear LocalStorage/IndexedDB. After clearing and reloading, the budget opened without issues.
GiteaMirror commented 2026-02-28 20:27:39 -06:00
Author
Owner
Copy Link

@dastone16 commented on GitHub (Feb 11, 2026):

Hi, I'm hitting a very similar "We had an unknown problem opening 'My-Finance---copy-3fa925b'" error in the local desktop app on Windows 11, using Actual version 26.2.0.

This started when reopening after approximately 11 days of inactivity. This is the second time this issue has occurred. Making a duplicate makes an openable copy that is usable for many weeks.

New budget files create/open without issue?
Yes. Duplicate of file (both for all devices and locally) produces file that can be opened without error.

This looks very similar, but that was on PikaPods after upgrade — mine is purely local desktop.

I'm unsure how to proceed to test if this is local corruption

Happy to provide more logs or test patches. Thanks!

@dastone16 commented on GitHub (Feb 11, 2026): Hi, I'm hitting a very similar "We had an unknown problem opening 'My-Finance---copy-3fa925b'" error in the local desktop app on Windows 11, using Actual version 26.2.0. This started when reopening after approximately 11 days of inactivity. This is the second time this issue has occurred. Making a duplicate makes an openable copy that is usable for many weeks. New budget files create/open without issue? Yes. Duplicate of file (both for all devices and locally) produces file that can be opened without error. This looks very similar, but that was on PikaPods after upgrade — mine is purely local desktop. I'm unsure how to proceed to test if this is local corruption Happy to provide more logs or test patches. Thanks!
GiteaMirror commented 2026-02-28 20:27:39 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 11, 2026):

Hi, I'm hitting a very similar "We had an unknown problem opening 'My-Finance---copy-3fa925b'" error in the local desktop app on Windows 11, using Actual version 26.2.0.

This started when reopening after approximately 11 days of inactivity. This is the second time this issue has occurred. Making a duplicate makes an openable copy that is usable for many weeks.

New budget files create/open without issue? Yes. Duplicate of file (both for all devices and locally) produces file that can be opened without error.

This looks very similar, but that was on PikaPods after upgrade — mine is purely local desktop.

I'm unsure how to proceed to test if this is local corruption

Happy to provide more logs or test patches. Thanks!

@dastone16 Don't use the deskop app if you have a hosted server. This like likely a version issue. Install the PWA via your browser if you want an app like experience.

@youngcw commented on GitHub (Feb 11, 2026): > Hi, I'm hitting a very similar "We had an unknown problem opening 'My-Finance---copy-3fa925b'" error in the local desktop app on Windows 11, using Actual version 26.2.0. > > This started when reopening after approximately 11 days of inactivity. This is the second time this issue has occurred. Making a duplicate makes an openable copy that is usable for many weeks. > > New budget files create/open without issue? Yes. Duplicate of file (both for all devices and locally) produces file that can be opened without error. > > This looks very similar, but that was on PikaPods after upgrade — mine is purely local desktop. > > I'm unsure how to proceed to test if this is local corruption > > Happy to provide more logs or test patches. Thanks! @dastone16 Don't use the deskop app if you have a hosted server. This like likely a version issue. Install the PWA via your browser if you want an app like experience.
GiteaMirror commented 2026-02-28 20:27:40 -06:00
Author
Owner
Copy Link

@dastone16 commented on GitHub (Feb 11, 2026):

Sorry - I may have described something incorrectly. I am using the desktop app. The version I see in bottom right corner is App: v26.2.0 | Server: v26.2.0

@dastone16 commented on GitHub (Feb 11, 2026): Sorry - I may have described something incorrectly. I am using the desktop app. The version I see in bottom right corner is App: v26.2.0 | Server: v26.2.0
GiteaMirror commented 2026-02-28 20:27:41 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 11, 2026):

Sorry - I may have described something incorrectly. I am using the desktop app. The version I see in bottom right corner is App: v26.2.0 | Server: v26.2.0

I know. Don't use the desktop app if you have a hosted server. It causes version issues if you do. Your versions are the same now, but there was likely a time that they weren't the same.

@youngcw commented on GitHub (Feb 11, 2026): > Sorry - I may have described something incorrectly. I am using the desktop app. The version I see in bottom right corner is App: v26.2.0 | Server: v26.2.0 I know. Don't use the desktop app if you have a hosted server. It causes version issues if you do. Your versions are the same now, but there was likely a time that they weren't the same.
GiteaMirror commented 2026-02-28 20:27:41 -06:00
Author
Owner
Copy Link

@dastone16 commented on GitHub (Feb 11, 2026):

@youngcw Thank you for your help.

With the versions the same I'm still getting the error: "We had an unknown problem opening 'My-Finance---copy-3fa925b'"

Is my only option to make a copy every time I get this error?

@dastone16 commented on GitHub (Feb 11, 2026): @youngcw Thank you for your help. With the versions the same I'm still getting the error: "We had an unknown problem opening 'My-Finance---copy-3fa925b'" Is my only option to make a copy every time I get this error?
GiteaMirror commented 2026-02-28 20:27:42 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 11, 2026):

The file may have been broken. Try the previous version or load a backup

@youngcw commented on GitHub (Feb 11, 2026): The file may have been broken. Try the previous version or load a backup
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 needs info
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#2778
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?