Hey everyone! I'm having a quirky issue with my self-hosted Actual Budget server, especially on mobile browsers. I've been trying to troubleshoot this for hours and I'm at my wit's end. Here's the setup: my server runs locally and is accessible via a domain with HTTPS through Caddy. On desktop, it works perfectly with LibreWolf and Firefox, but here's the catch—on mobile, I'm facing a 'shared buffer array' error on several browsers like Firefox, IronFox, DuckDuckGo, and Chromite, while Edge mobile works just fine. I suspect it's more about how different browsers handle SharedArrayBuffer rather than a server-side issue since the necessary CORS headers are already configured. So I'm wondering, has anyone encountered compatibility issues with SharedArrayBuffer on mobile? Any tips on additional headers or potential workarounds for privacy-focused browsers? Thanks a ton for any help!
2 Answers
It sounds like you’re leaning towards it being a browser issue due to the variation in how different browsers handle SharedArrayBuffer. There’s a chance your code could have a bug as well since it works on Edge. It's worth double-checking your implementation to make sure everything is set up correctly. Sometimes, browser security measures can also trip things up, so don't discount that possibility!
This is more about browser support differences. Edge is known to be forgiving with shared buffers, while mobile versions of Chrome and Firefox require stricter CORS headers. Have you tried setting 'Cross-Origin-Embedder-Policy: require-corp' and 'Cross-Origin-Opener-Policy: same-origin'? Restart your server after applying those settings and see if that makes a difference!
Thanks for suggesting that! But I did already set those headers and verified they’re configured correctly. Still no luck.
I appreciate your input! Definitely will look into the code. It's just strange that it works on desktop and only Edge on mobile. Might be worth reviewing specific examples for guidance.