[GH-ISSUE #7795] [Bug]: Enable Banking works in Chromium but not in Firefox #117582

Closed
opened 2026-06-11 12:58:39 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @daneov on GitHub (May 11, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7795

What happened?

I was trying to set up banking using the sha-e479c84-alpine image when going through the Set up banking flow with Enable Banking credentials. I selected Enable Banking -> Set up and provided the Application ID some_uuid together with some_uuid.pem returned by Enable Banking.

Expected: the banking setup flow completes successfully and linked accounts are available.

Actual: the flow fails during authentication/setup on Firefox, but works on Chromium even though the application details are set exactly the same.

Error message:

Could not validate the credentials. Please check your Application ID and secret key.

As far as I can see from the code, this would only happen if something is going wrong with the userToken from session storage. This seems to be browser specific, maybe some API needs to be called just a bit differently?

How can we reproduce the issue?

  1. Go to your Actual website using Firefox (my version is 147.0.2)
  2. Enable Enable Banking in the feature flags
  3. Go to Bank sync
  4. Enter the uuid as shown on Enable Banking
  5. Upload the <uuid.pem> file, as provided by Enable Banking
  6. Press the "Save and continue" button
  7. Observe the error

Using the same steps in Chromium works, potentially (but unverified) pointing to using a webkit-specific API? Unsure.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @daneov on GitHub (May 11, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7795 ### What happened? I was trying to set up banking using the `sha-e479c84-alpine` image when going through the `Set up banking` flow with Enable Banking credentials. I selected `Enable Banking -> Set up` and provided the Application ID `some_uuid` together with `some_uuid.pem` returned by Enable Banking. Expected: the banking setup flow completes successfully and linked accounts are available. Actual: the flow fails during authentication/setup on Firefox, but works on Chromium even though the application details are set exactly the same. Error message: ```text Could not validate the credentials. Please check your Application ID and secret key. ``` As far as I can see from the code, this would only happen if something is going wrong with the `userToken` from session storage. This seems to be browser specific, maybe some API needs to be called just a bit differently? ### How can we reproduce the issue? 1. Go to your Actual website using Firefox (my version is 147.0.2) 2. Enable `Enable Banking` in the feature flags 3. Go to `Bank sync` 4. Enter the uuid as shown on Enable Banking 5. Upload the `<uuid.pem>` file, as provided by Enable Banking 6. Press the "Save and continue" button 7. Observe the error Using the same steps in Chromium works, potentially (but unverified) pointing to using a webkit-specific API? Unsure. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-06-11 12:58:39 -05:00
Author
Owner

@matt-fidd commented on GitHub (May 12, 2026):

Please post this in https://github.com/actualbudget/actual/issues/7799

<!-- gh-comment-id:4434781666 --> @matt-fidd commented on GitHub (May 12, 2026): Please post this in https://github.com/actualbudget/actual/issues/7799
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117582