[Bug]: We had an unknown problem opening "<local actual file>"

[mt-TechJourney]

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

[josecannete]

Same problem here, I've downgraded to 2.4.7.

[psybers]

This is a duplicate of #2705.

[MatissJanis]

@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

[Gazook89]

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

[haufhun]

Same issue here as well

[MikesGlitch]

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.

[olets]

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)

[MikesGlitch]

Note: i've posted this message here as well as they seem like similar 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

[psybers]

@MikesGlitch x86 works

[mt-TechJourney]

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

[MikesGlitch]

@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

[mt-TechJourney]

@MikesGlitch

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

[MikesGlitch]

@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: electron-userland/electron-builder#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.

[kennydrobnack]

@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")

[MikesGlitch]

@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

[kennydrobnack]

@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.

[melz]

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.

[MikesGlitch]

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

[MikesGlitch]

Fixed by #3220

[asherljh]

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!