github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-13 17:43:23 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #7509] [Bug]: SharedBufferArray error on mobile browsers. (Firefox, DDG, Cromite, Ironfox) #117478

New Issue
Closed
opened 2026-06-11 12:41:31 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-11 12:41:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @GeoSabreX on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7509

What happened?

I’m hosting Actual Budget on my own server and accessing it from a mobile browser. It should load and work normally like it does on desktop and in Edge mobile, but on several mobile browsers it fails to load and throws a SharedArrayBuffer-related error instead. The app never fully initializes. It does offer the "bypass anyway" option, but from reading the documentation this will likely break the data synchronization between multiple accessed clients.

The error message varies a bit depending on the browser, but it’s along the lines of “SharedArrayBuffer is not defined” or “Shared buffer array is not available.”

Cromite says - Fatal Error, There was a problem loading the app in this browser version.

DDG, IronFox, and Firefox say - Fatal Error, Actual requires access to SharedArrayBuffer in order to function properly. If you're seeing this error, either your browser does not support SharedArrayBuffer, or your server is not sending the appropriate headers, or you are not using HTTPS. See our troubleshooting documentation to learn more. Advanced options.

How can we reproduce the issue?

  1. Host Actual Budget on a server
  2. Put it behind a reverse proxy (I’m using Caddy) with HTTPS enabled
  3. Open the site on a mobile device using Firefox mobile, DuckDuckGo Browser, Chromite, or IronFox
  4. Observe that the app fails to load and shows a SharedArrayBuffer-related error
  5. Add the headers Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp
  6. Try again on the same browsers — the behavior does not change and the same error occurs

Control test:
7. Open the exact same URL on the same device using Edge mobile
8. The app loads and works normally

Note: I was getting this error before adding the headers, and adding them didn’t change anything.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Other

Operating System

Mobile Device

Originally created by @GeoSabreX on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7509 ### What happened? I’m hosting Actual Budget on my own server and accessing it from a mobile browser. It should load and work normally like it does on desktop and in Edge mobile, but on several mobile browsers it fails to load and throws a SharedArrayBuffer-related error instead. The app never fully initializes. It does offer the "bypass anyway" option, but from reading the documentation this will likely break the data synchronization between multiple accessed clients. The error message varies a bit depending on the browser, but it’s along the lines of “SharedArrayBuffer is not defined” or “Shared buffer array is not available.” Cromite says - Fatal Error, There was a problem loading the app in this browser version. DDG, IronFox, and Firefox say - Fatal Error, Actual requires access to SharedArrayBuffer in order to function properly. If you're seeing this error, either your browser does not support SharedArrayBuffer, or your server is not sending the appropriate headers, or you are not using HTTPS. See our troubleshooting documentation to learn more. Advanced options. ### How can we reproduce the issue? 1. Host Actual Budget on a server 2. Put it behind a reverse proxy (I’m using Caddy) with HTTPS enabled 3. Open the site on a mobile device using Firefox mobile, DuckDuckGo Browser, Chromite, or IronFox 4. Observe that the app fails to load and shows a SharedArrayBuffer-related error 5. Add the headers Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp 6. Try again on the same browsers — the behavior does not change and the same error occurs Control test: 7. Open the exact same URL on the same device using Edge mobile 8. The app loads and works normally Note: I was getting this error before adding the headers, and adding them didn’t change anything. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Other ### Operating System Mobile Device
GiteaMirror added the bugresponsive labels 2026-06-11 12:41:38 -05:00
GiteaMirror commented 2026-06-11 12:41:44 -05:00
Author
Owner
Copy Link
Copy Source

@matt-fidd commented on GitHub (Apr 15, 2026):

I can't replicate on iOS wth Firefox, but I believe they use webkit under the hood on all browsers. Are you using an android device?

<!-- gh-comment-id:4251227073 --> @matt-fidd commented on GitHub (Apr 15, 2026): I can't replicate on iOS wth Firefox, but I believe they use webkit under the hood on all browsers. Are you using an android device?
GiteaMirror commented 2026-06-11 12:41:46 -05:00
Author
Owner
Copy Link
Copy Source

@GeoSabreX commented on GitHub (Apr 15, 2026):

I can't replicate on iOS wth Firefox, but I believe they use webkit under the hood on all browsers. Are you using an android device?

Yes, I am using Android on a Samsung Galaxy S25 Ultra. I expect things to break with the privacy focused browsers, especially Cromite, since they disable so many tools by default. But vanilla Firefox failing seems indicative of a bigger issue here.

<!-- gh-comment-id:4251736098 --> @GeoSabreX commented on GitHub (Apr 15, 2026): > I can't replicate on iOS wth Firefox, but I believe they use webkit under the hood on all browsers. Are you using an android device? Yes, I am using Android on a Samsung Galaxy S25 Ultra. I expect things to break with the privacy focused browsers, especially Cromite, since they disable so many tools by default. But vanilla Firefox failing seems indicative of a bigger issue here.
GiteaMirror commented 2026-06-11 12:41:48 -05:00
Author
Owner
Copy Link
Copy Source

@MatissJanis commented on GitHub (Apr 19, 2026):

Most likely Caddy config likely isn't applying COOP/COEP to all responses. Either way - this isn't really a bug report, but more of a tech support conversation. For those: please use the community Discord. We try to keep github issues only for real bug reports.

<!-- gh-comment-id:4276803891 --> @MatissJanis commented on GitHub (Apr 19, 2026): Most likely Caddy config likely isn't applying COOP/COEP to all responses. Either way - this isn't really a bug report, but more of a tech support conversation. For those: please use the community Discord. We try to keep github issues only for real bug reports.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels bug responsive
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117478