[GH-ISSUE #3199] [Bug]: We had an unknown problem opening "<local actual file>" #90930

New Issue

GiteaMirror · 2026-05-25T21:01:03-05:00

GiteaMirror commented

2026-05-25 21:01:03 -05:00

Originally created by @ghost on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3199

Verified issue does not already exist?

I have searched and found no existing issue
I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

This is my local actual db that I use to manage my finances.

After the latest update (v24.8.0) which I downloaded from the GitHub repository, the application fails to read my database and gives me an error.

Even if I try to create a new local actual file, it is still giving me the same error as shown in the screenshot above. I have installed the previous version for now since that is not giving me an error (v24.7.0)

Where are you hosting Actual?

Desktop App (Electron)

What browsers are you seeing the problem on?

Other

Operating System

Mac OSX

Originally created by @ghost on GitHub (Aug 4, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3199 ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? This is my local actual db that I use to manage my finances. ![Untitled](https://github.com/user-attachments/assets/7e987270-87d0-4a1f-ab00-8740660027b4) After the latest update (v24.8.0) which I downloaded from the GitHub repository, the application fails to read my database and gives me an error. <img width="901" alt="image" src="https://github.com/user-attachments/assets/bdab0fe9-823f-4241-961c-31b19452c44c"> Even if I try to create a new local actual file, it is still giving me the same error as shown in the screenshot above. I have installed the previous version for now since that is not giving me an error (v24.7.0) ### Where are you hosting Actual? Desktop App (Electron) ### What browsers are you seeing the problem on? Other ### Operating System Mac OSX

GiteaMirror added the bug label 2026-05-25 21:01:03 -05:00

GiteaMirror closed this issue

2026-05-25 21:01:05 -05:00

GiteaMirror commented

2026-05-25 21:01:07 -05:00

@josecannete commented on GitHub (Aug 4, 2024):

Same problem here, I've downgraded to 2.4.7.

@josecannete commented on GitHub (Aug 4, 2024): Same problem here, I've downgraded to 2.4.7.

GiteaMirror commented

2026-05-25 21:01:07 -05:00

@psybers commented on GitHub (Aug 6, 2024):

This is a duplicate of #2705.

@psybers commented on GitHub (Aug 6, 2024): This is a duplicate of #2705.

GiteaMirror commented

2026-05-25 21:01:09 -05:00

@MatissJanis commented on GitHub (Aug 6, 2024):

@psybers that's a very similar bug, but I think the root cause might be different.

#2705 - CI runners building bad osx images (both intel and m1)

#3199 - my local build (we're not using the CI runner builds for the releases/downloads page due to #2705) - works on intel, broken on m1 since 24.8.0

@MatissJanis commented on GitHub (Aug 6, 2024): @psybers that's a very similar bug, but I think the root cause might be different. #2705 - CI runners building bad osx images (both intel and m1) #3199 - my local build (we're not using the CI runner builds for the releases/downloads page due to #2705) - works on intel, broken on m1 since 24.8.0

GiteaMirror commented

2026-05-25 21:01:10 -05:00

@Gazook89 commented on GitHub (Aug 6, 2024):

I have this same issue. I just got started with Actual for the first time last night so I can't comment on changes over time, but will be going with the previous version for now.

On MacOS, Silicon, M3 Pro

@Gazook89 commented on GitHub (Aug 6, 2024): I have this same issue. I just got started with Actual for the first time last night so I can't comment on changes over time, but will be going with the previous version for now. On MacOS, Silicon, M3 Pro

GiteaMirror commented

2026-05-25 21:01:11 -05:00

@haufhun commented on GitHub (Aug 6, 2024):

Same issue here as well

@haufhun commented on GitHub (Aug 6, 2024): Same issue here as well

GiteaMirror commented

2026-05-25 21:01:12 -05:00

@MikesGlitch commented on GitHub (Aug 6, 2024):

Would anyone be able to reproduce the error on the latest build and then run the following steps:

Use shortcut Cmd+Alt+I
Click on the "Console" tab of the window that opens
Press F5 (to refresh the page)
Then copy the contents of the "Console"

If you can paste the contents of the console in here it will help those of us without a mac.

@MikesGlitch commented on GitHub (Aug 6, 2024): Would anyone be able to reproduce the error on the latest build and then run the following steps: - Use shortcut Cmd+Alt+I - Click on the "Console" tab of the window that opens ![image](https://github.com/user-attachments/assets/7c2f3b01-8a52-4027-adb9-ad1ba52eb717) - Press F5 (to refresh the page) - Then copy the contents of the "Console" If you can paste the contents of the console in here it will help those of us without a mac.

GiteaMirror commented

2026-05-25 21:01:13 -05:00

@olets commented on GitHub (Aug 6, 2024):

On Sonoma 14.5, F5 after opening the developer tools doesn't trigger a reload for me. I can trigger a reload by

opening the developer tools
clicking on the developer tools
shift-command-p
typing "reload"
clicking "reload page"

(no console messages to share because I'm on 24.7.0. Waiting for #2907 so I can make a backup before trying an upgrade)

@olets commented on GitHub (Aug 6, 2024): On Sonoma 14.5, F5 after opening the developer tools doesn't trigger a reload for me. I can trigger a reload by 1. opening the developer tools 2. clicking on the developer tools 3. shift-command-p 4. typing "reload" 5. clicking "reload page" (no console messages to share because I'm on 24.7.0. Waiting for #2907 so I can make a backup before trying an upgrade)

GiteaMirror commented

2026-05-25 21:01:15 -05:00

@MikesGlitch commented on GitHub (Aug 9, 2024):

Note: i've posted this message here as well as they seem like similar issues - https://github.com/actualbudget/actual/issues/2705

I've got a fresh build up here: https://github.com/actualbudget/actual/actions/runs/10319828575?pr=3220

I'm looking for 2 testers, one with a x64 machine and one with an arm64 machine.

I'm expecting the x64 machine to work and the arm64 machine to fail - but want to double check before I try anything else.

For the testers:

Can you install the dmg file appropriate for your arch - there's 2: x64 and arm64

@MikesGlitch commented on GitHub (Aug 9, 2024): Note: i've posted this message here as well as they seem like similar issues - https://github.com/actualbudget/actual/issues/2705 I've got a fresh build up here: https://github.com/actualbudget/actual/actions/runs/10319828575?pr=3220 I'm looking for 2 testers, one with a x64 machine and one with an arm64 machine. I'm expecting the x64 machine to work and the arm64 machine to fail - but want to double check before I try anything else. For the testers: - Can you install the dmg file appropriate for your arch - there's 2: x64 and arm64

GiteaMirror commented

2026-05-25 21:01:17 -05:00

@psybers commented on GitHub (Aug 9, 2024):

@MikesGlitch x86 works

@psybers commented on GitHub (Aug 9, 2024): @MikesGlitch x86 works

GiteaMirror commented

2026-05-25 21:01:18 -05:00

@ghost commented on GitHub (Aug 9, 2024):

@MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

@ghost commented on GitHub (Aug 9, 2024): @MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

GiteaMirror commented

2026-05-25 21:01:19 -05:00

@MikesGlitch commented on GitHub (Aug 9, 2024):

@MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

Sweet - can you try this one with your arm64 cpu?

https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

@MikesGlitch commented on GitHub (Aug 9, 2024): > @MikesGlitch The x64 is working on my M1 Pro but the arm64 is not. Sweet - can you try this one with your arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

GiteaMirror commented

2026-05-25 21:01:20 -05:00

@ghost commented on GitHub (Aug 10, 2024):

@MikesGlitch

Getting this error for the arm64. The other one (x64) is working.

@ghost commented on GitHub (Aug 10, 2024): @MikesGlitch ![image](https://github.com/user-attachments/assets/9996c152-95b3-46a3-9f87-f8e82f258299) Getting this error for the arm64. The other one (x64) is working.

GiteaMirror commented

2026-05-25 21:01:21 -05:00

@MikesGlitch commented on GitHub (Aug 10, 2024):

@MikesGlitch

Getting this error for the arm64. The other one (x64) is working.

Thanks for checking. I think this may have to do with this: https://github.com/electron-userland/electron-builder/issues/8191

The article says you can get around it by running this command on your mac, can you give it a go?

 xattr -c <path/to/application.app>

It says it has something to do with app notarization, which we plan on fixing but need to make sure the builds are functioning first.

@MikesGlitch commented on GitHub (Aug 10, 2024): > @MikesGlitch > > ![image](https://private-user-images.githubusercontent.com/177056470/356790171-9996c152-95b3-46a3-9f87-f8e82f258299.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMyODA1NDcsIm5iZiI6MTcyMzI4MDI0NywicGF0aCI6Ii8xNzcwNTY0NzAvMzU2NzkwMTcxLTk5OTZjMTUyLTk1YjMtNDZhMy05Zjg3LWY4ZTgyZjI1ODI5OS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgxMFQwODU3MjdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hNDVmYmQyZDNlODdhMWE1ZmYyMjE0MmE5Y2ZlNGUyYzU1MzQ5MGRiZWRlMmViMjI2YjVmOTMzZmJmNzdkYWY1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.VjJuZTpU3KOEsRwWulHfi-rTA3JNC_PA3koQ8JnlRMg) > > Getting this error for the arm64. The other one (x64) is working. Thanks for checking. I think this _may_ have to do with this: https://github.com/electron-userland/electron-builder/issues/8191 The article says you can get around it by running this command on your mac, can you give it a go? ``` xattr -c <path/to/application.app> ``` It says it has something to do with app notarization, which we plan on fixing but need to make sure the builds are functioning first.

GiteaMirror commented

2026-05-25 21:01:22 -05:00

@kennydrobnack commented on GitHub (Aug 11, 2024):

@MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

Sweet - can you try this one with your arm64 cpu?

https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged.

After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version.

Here's the full error message:

console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n")

@kennydrobnack commented on GitHub (Aug 11, 2024): > > @MikesGlitch The x64 is working on my M1 Pro but the arm64 is not. > > Sweet - can you try this one with your arm64 cpu? > > https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220 I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged. After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version. Here's the full error message: console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n")

GiteaMirror commented

2026-05-25 21:01:23 -05:00

@MikesGlitch commented on GitHub (Aug 11, 2024):

@MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

Sweet - can you try this one with your arm64 cpu?
https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged.

After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version.

Here's the full error message:

console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n")

I noticed a electron-rebuild was saying it succeeded when it didn't do anything. I think I fixed it.

Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

@MikesGlitch commented on GitHub (Aug 11, 2024): > > > @MikesGlitch The x64 is working on my M1 Pro but the arm64 is not. > > > > > > Sweet - can you try this one with your arm64 cpu? > > https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220 > > I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged. > > After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version. > > Here's the full error message: > > console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n") I noticed a electron-rebuild was saying it succeeded when it didn't do anything. I think I fixed it. Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

GiteaMirror commented

2026-05-25 21:01:24 -05:00

@kennydrobnack commented on GitHub (Aug 11, 2024):

@MikesGlitch The x64 is working on my M1 Pro but the arm64 is not.

Sweet - can you try this one with your arm64 cpu?
https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220

I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged.
After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version.
Here's the full error message:
console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n")

I noticed a electron-rebuild was saying it succeeded when it didn't do anything. I think I fixed it.

Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

I haven't had a chance to put it through its paces, but it is able to open a budget from my Actual server. Looks like it's fixed. Thanks!

EDIT to add: I still had to do the xattr -c thing to get around the "app is damaged" error. Sorry I forgot to mention that earlier.

@kennydrobnack commented on GitHub (Aug 11, 2024): > > > > @MikesGlitch The x64 is working on my M1 Pro but the arm64 is not. > > > > > > > > > Sweet - can you try this one with your arm64 cpu? > > > https://github.com/actualbudget/actual/actions/runs/10322929844?pr=3220 > > > > > > I tried this and had to use the xattr -c command on the .app to get around the error message saying the app is damaged. > > After I got into the console logs, it's pretty clear what's going on. Some part of the app is using Intel bits instead of arm. I triple checked to make sure the app I was running is the Apple Silicon version. > > Here's the full error message: > > console.error('Server Log:', "[Exception] Error: dlopen(/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0, 0x0001): tried: '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (no such file), '/private/var/folders/3q/f_7507pn20d28hc11nlvntb80000gn/T/.com.actualbudget.actual.aULCS0' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)\n at Module._extensions..node (node:internal/modules/cjs/loader:1489:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2441)\n at Module.load (node:internal/modules/cjs/loader:1214:32)\n at Module._load (node:internal/modules/cjs/loader:1030:12)\n at c._load (node:electron/js2c/node_init:2:13672)\n at Module.require (node:internal/modules/cjs/loader:1242:19)\n at require (node:internal/modules/helpers:176:18)\n at bindings (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/bindings/bindings.js:112:48)\n at new Database (/Applications/Actual.app/Contents/Resources/app.asar/node_modules/better-sqlite3/lib/database.js:48:64) {\n code: 'ERR_DLOPEN_FAILED'\n}\n") > > I noticed a electron-rebuild was saying it succeeded when it didn't do anything. I think I fixed it. > > Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220 I haven't had a chance to put it through its paces, but it is able to open a budget from my Actual server. Looks like it's fixed. Thanks! EDIT to add: I still had to do the xattr -c thing to get around the "app is damaged" error. Sorry I forgot to mention that earlier.

GiteaMirror commented

2026-05-25 21:01:24 -05:00

@melz commented on GitHub (Aug 12, 2024):

Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220

Just tried this the arm64 on a M2. I also had to execute the xattr -c command on the .app to get around the error message saying the app is damaged but it does work after.

@melz commented on GitHub (Aug 12, 2024): > Can someone try this one on an arm64 cpu? https://github.com/actualbudget/actual/actions/runs/10339466938?pr=3220 Just tried this the arm64 on a M2. I also had to execute the `xattr -c` command on the .app to get around the error message saying the app is damaged but it does work after.

GiteaMirror commented

2026-05-25 21:01:25 -05:00

@MikesGlitch commented on GitHub (Aug 12, 2024):

I have a PR up with the fix, thanks for the help everyone! 🚀

@MikesGlitch commented on GitHub (Aug 12, 2024): I have a PR up with the fix, thanks for the help everyone! 🚀

GiteaMirror commented

2026-05-25 21:01:26 -05:00

@MikesGlitch commented on GitHub (Aug 12, 2024):

Fixed by https://github.com/actualbudget/actual/pull/3220

@MikesGlitch commented on GitHub (Aug 12, 2024): Fixed by https://github.com/actualbudget/actual/pull/3220

GiteaMirror commented

2026-05-25 21:01:27 -05:00

@asherljh commented on GitHub (Sep 26, 2024):

Hi there, I'm running v24.9.0 but am still running into this issue. Interestingly, I encounter "We had an unknown problem opening "My-Finances-79046ea" on Firefox on my AMD computer, and my Xiaomi 14, but not on Firefox on my Zenfone 9.

On my computer, it works in the Actual desktop app.

If I create a new file / import my data from the Actual exported .zip, I will be able to access the file for a short while but after I refresn the page a few times I will end up with the error again. Any help? Thanks!

Edit: May have figured it out, I deleted and re-imported a file with the same name across all devices while some (e.g. maybe my old phone, or a chrome tab I used to test it) still had the file open. I deleted the file and made sure i closed Actual on all my devices, synced it, and imported the file back. Seems to be working for now. Sorry for the trouble. Love the app!

@asherljh commented on GitHub (Sep 26, 2024): Hi there, I'm running v24.9.0 but am still running into this issue. Interestingly, I encounter "We had an unknown problem opening "My-Finances-79046ea" on Firefox on my AMD computer, and my Xiaomi 14, but not on Firefox on my Zenfone 9. ![image](https://github.com/user-attachments/assets/dfb48491-43b4-410f-a031-1b2454711bf6) On my computer, it works in the Actual desktop app. If I create a new file / import my data from the Actual exported .zip, I will be able to access the file for a short while but after I refresn the page a few times I will end up with the error again. Any help? Thanks! Edit: May have figured it out, I deleted and re-imported a file with the same name across all devices while some (e.g. maybe my old phone, or a chrome tab I used to test it) still had the file open. I deleted the file and made sure i closed Actual on all my devices, synced it, and imported the file back. Seems to be working for now. Sorry for the trouble. Love the app!

GiteaMirror commented

2026-05-25 21:01:28 -05:00

@T3chGuy77 commented on GitHub (Apr 18, 2025):

This issue is not fixed or resolved. I still have it on the current version.

@T3chGuy77 commented on GitHub (Apr 18, 2025): This issue is not fixed or resolved. I still have it on the current version.

GiteaMirror commented

2026-05-25 21:01:29 -05:00

@MikesGlitch commented on GitHub (Apr 18, 2025):

This issue is not fixed or resolved. I still have it on the current version.

What do you see when you open devtools? It's under the View menu > Toggle developer tools.

Can you copy and paste the error here?

@MikesGlitch commented on GitHub (Apr 18, 2025): > This issue is not fixed or resolved. I still have it on the current version. What do you see when you open devtools? It's under the View menu > Toggle developer tools. Can you copy and paste the error here?

GiteaMirror commented

2026-05-25 21:01:30 -05:00

@mehrmoudi commented on GitHub (May 18, 2025):

I just ran into this issue. It doesn't happen the first time I open the budget and it downloads it. But every time after it keeps happening. I have to clear browser data/cache to be able to work with my budget.

I see the following message in the console:

[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 loadSpreadsheet (sheet.ts:153:30)
    at budgetfiles_app_loadBudget (app.ts:590:11)
    at async app_loadBudget (app.ts:239:15)

Versions: App: v25.5.0 | Server: v25.5.0

@mehrmoudi commented on GitHub (May 18, 2025): I just ran into this issue. It doesn't happen the first time I open the budget and it downloads it. But every time after it keeps happening. I have to clear browser data/cache to be able to work with my budget. I see the following message in the console: ``` [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 loadSpreadsheet (sheet.ts:153:30) at budgetfiles_app_loadBudget (app.ts:590:11) at async app_loadBudget (app.ts:239:15) ``` Versions: `App: v25.5.0 | Server: v25.5.0`

GiteaMirror commented

2026-05-25 21:01:30 -05:00

@MuffinBeast commented on GitHub (May 26, 2025):

Just installed ActualServer, v25.5.0 on unraid, and started using it today for the first time - ran into this error when trying to get back into my file.

This is my output from Firefox dev tools:

@MuffinBeast commented on GitHub (May 26, 2025): Just installed ActualServer, v25.5.0 on unraid, and started using it today for the first time - ran into this error when trying to get back into my file. This is my output from Firefox dev tools: Error updating Error: table preferences already exists handleError http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 exec http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:16 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 1723665565000 http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:297 applyJavaScript http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 applyMigration http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 [kcab.worker.b147f857d4768d8c57e5.js:304:10987](http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js) [Exception] Error: table preferences already exists handleError http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 exec http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:16 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 1723665565000 http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:297 applyJavaScript http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 applyMigration http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 [kcab.worker.b147f857d4768d8c57e5.js:16:206248](http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js) Error updating budget My-Finances-ea433d7 Error: table preferences already exists handleError http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 exec http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:16 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 1723665565000 http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:297 applyJavaScript http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 applyMigration http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 [kcab.worker.b147f857d4768d8c57e5.js:104:2662](http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js) Error updating budget Error: table preferences already exists handleError http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 exec http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:6 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:16 execQuery http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 1723665565000 http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:297 applyJavaScript http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 applyMigration http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js:301 [kcab.worker.b147f857d4768d8c57e5.js:304:11242](http://10.0.0.2:5006/kcab/kcab.worker.b147f857d4768d8c57e5.js) triggering sync because of visibility change

GiteaMirror commented

2026-05-25 21:01:30 -05:00

@MikesGlitch commented on GitHub (May 26, 2025):

Just so everyone knows, that error in that screenshot in the description is a catch-all error. The initial issue here was to do with how better-sqlite was built - which is fixed.

To keep our Github clean(ish) and to give your issues more attention, can you please open a new issue with the information form the devtools logs. There's no point in adding comments to this Issue becuase there's loads of potential problems related to this one user-facing error. We can't tackle them all in one issue.

@MuffinBeast That one looks like a migration error. First thing to do is ensure you have HTTPS setup/running from localhost.

@MikesGlitch commented on GitHub (May 26, 2025): Just so everyone knows, that error in that screenshot in the description is a catch-all error. The initial issue here was to do with how better-sqlite was built - which is fixed. To keep our Github clean(ish) and to give your issues more attention, can you please open a new issue with the information form the devtools logs. There's no point in adding comments to this Issue becuase there's loads of potential problems related to this one user-facing error. We can't tackle them all in one issue. @MuffinBeast That one looks like a migration error. First thing to do is ensure you have HTTPS setup/running from localhost.

Sign in to join this conversation.

Branches Tags

master

dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a

enforce-append-only-migrations-ci

claude/error-codes-worker-boundary-26i5uu

api-browser-custom-data-dir

tabedzki/feat/replacing-month-picker-with-day-picker

delay-initial-sync-until-loaded

jfdoming/mobile-app-build

cross-version-sync-compat

jfdoming/api-tokens-part-1

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-3

jfdoming/mobile-app-updates

claude/budget-version-migration-compat-151jlr

claude/worker-error-serialization-9iqtl7

claude/react-table-library-research-afx83z

claude/issue-8401-regression-test-9nw9l3

jfdoming/mobile-app-foundation-part-1

jfdoming/mobile-app-scaffold

release

ai-fix-cleanup-def-8290

claude/relaxed-shannon-jusywa

claude/fervent-keller-s6f2fq

claude/determined-feynman-st1y9z

claude/wizardly-einstein-vi2wce

claude/sweet-albattani-7nseio

feat/bank-sync-per-budget-file

claude/affectionate-cannon-y0kc82

claude/dependabot-findings-m9pgmb

claude/mac-app-ios-publish-zjs1lz

claude/vigilant-tesla-aiiyos

depot-migrate-secrets-1781296330308

claude/quirky-cerf-v5qck7

claude/animation-removal-alternative-2etfh1

claude/netlify-preview-comments-consolidate-9XPYa

osc/7391-error-boundaries-reports

claude/pensive-dijkstra-7DYui

claude/server-app-version-mismatch-HTCGv

claude/pr-8027-review-feedback-mELuO

claude/zealous-wozniak-e5pO0

claude/intelligent-heisenberg-BSHJq

claude/translation-download-refactor-jFRsO

claude/mobile-performance-ideas-G9PAO

claude/github-issue-7988-5A5ly

blacksmith-migration-ff70d2d

claude/great-mayer-KRvOk

claude/react-native-ios-compilation-fcJh5

claude/serene-goldberg-58xv0

claude/kind-euler-LVG3K

release-automation/edge-nightly

7710-bundle-migrations

claude/fix-docker-build-error-WMfed

claude/llm-compatible-release-notes-t20Nr

7710-tests-tdd

cursor/transaction-table-rewrite-f077

claude/plan-ci-secure-context-OtEe1

claude/fix-issue-7667-DPXi3

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

claude/api-consumer-verification-kfz1K

pr-7454

claude/fix-issue-7410-LLLQ4

revert-7281-generate-icons

react-query-useSchedules

copilot/sub-pr-6140

package-upgrades

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#90930