mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 11:59:55 -05:00
Closed
opened 2026-06-11 13:04:52 -05:00 by GiteaMirror
·
16 comments
No Branch/Tag Specified
master
tabedzki/feat/replacing-month-picker-with-day-picker
enforce-append-only-migrations-ci
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
claude/error-codes-worker-boundary-26i5uu
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
ai/simplify-categories-get-api
api-browser-custom-data-dir
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
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
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
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#117645
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KevinIsMyName on GitHub (Jun 1, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8023
What happened?
I upgraded from v26.5.2 to v26.6.0. I was trying to "Bank Sync" in "All Accounts" and it failed. "All Accounts" use one SimpleFIN connection; none are local. I deleted the existing SimpleFIN connection, re-created and configured a new SimpleFIN token, and clicked "Link bank account" to test its connection and see if my financial institutions show up.
Expected: Bank Sync updates when using SimpleFIN
Actual: Fails to update.
Expected: Entering a new SimpleFIN token in Bank Setup > SimpleFIN > Edit setup with the "Set-up SimpleFIN" modal and then clicking "Link a new bank account" should show my financial institutions
Actual: Clicking "Link a new bank account" opens the "Set-up SimpleFIN" modal instead of showing my financial institutions
How can we reproduce the issue?
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Windows 11
@KevinIsMyName commented on GitHub (Jun 1, 2026):
FYI, I have stood up an alternate Docker instance with v26.5.2 to test the same SimpleFIN connection (with same token) and I was not able to reproduce this.
@matt-fidd commented on GitHub (Jun 1, 2026):
@youngcw do you use SimpleFIN on nightly?
@youngcw commented on GitHub (Jun 1, 2026):
Simplefin is working fine for me. I haven't tried adding new connection though
@KevinIsMyName commented on GitHub (Jun 1, 2026):
Could you try it with an budget upgraded from 26.5.2->26.6.0? I set up two new instances aside from my production instance, v26.6.0 and v26.5.2, and they both have their own SimpleFIN tokens and all pull from SimpleFIN successfully, but not my production instance, which was upgraded 26.5.2->26.6.0 today. All three instances have different SimpleFIN tokens.
I can live with promoting the new 26.6.0 instance to production. It's a few days out-of-date, but bank sync works. I will continue looking for the root cause in the meantime
@youngcw commented on GitHub (Jun 1, 2026):
I don't know what would be different. My instance has been upgraded from 26.5.2 to 26.6, just incrementally. That error looks like your server itself cant access simplefin. Have you tried restarting your server? Docker can randomly have networking troubles.
@KevinIsMyName commented on GitHub (Jun 1, 2026):
I'm not sure either. I have restarted the production instance and had no luck. I'm going to set up the dev envand see if I can get a good stack trace. This is the error from my production logs:
Perhaps the existing accessKey isn't being reset with a new connection? Totally shooting in the dark here...
I'll report back with my findings soon
@matt-fidd commented on GitHub (Jun 1, 2026):
That looks like SimpleFIN returning 403 Forbidden, it would point towards an invalid token somewhere
@good-pm commented on GitHub (Jun 1, 2026):
For what it's worth, I'm experiencing the same issue on 26.6.0. I don't really know what I'm looking at in Dev Tools > Network but can provide that output if someone can point me to what's useful. Far as I can tell I get a {"status":"ok"} response as well.
I've created a new application in SimpleFIN, pasted the token into AB, but in SimpleFIN the token still shows as "Unclaimed" with a null Last Used date.
@Juulz commented on GitHub (Jun 1, 2026):
I've been on nightly for a while. I'll update to latest and see what happens.
@Juulz commented on GitHub (Jun 1, 2026):
It was a bit of a fight to get it to update ( I was on the newest nightly ), but after an import it was fine. SimpleFIN synced with no errors.
@good-pm commented on GitHub (Jun 1, 2026):
Alright I got it to work by deleting the stale simplefin_accessKey from the db. After doing that, a new SimpleFIN token works as expected.
@KevinIsMyName commented on GitHub (Jun 1, 2026):
@good-pm , if you hit F12 or Ctrl + Shift + I, an extra window pane should pop out. You can also right-click on the page and look for Developer Tools > Inspect
OK, took me quite some digging. I found out my token was good, but my existing accessKey was bad and not being refreshed with the new token. You can reproduce this bug by going into the
../data/server-files/account.sqlite/as root and setting thesecrets.simplefin_accessKeyto a bad value (e.g. set it toabc123). When you "Reset SimpleFIN credentials", it gives you this error, despite the API request successfully setting simplefin_token to null.When you reset credentials, shouldn't it also set secrets.simplefin_accessKey to null?
Anyways, I fixed this by taking my token and manually creating my accessKey with the SimpleFIN protocol guide here. Then, I inserted both the token and accessKey into
../data/server-files/account.sqlite/. Now when I click "Link bank accounts", I see them!@matt-fidd commented on GitHub (Jun 1, 2026):
Really odd that upgrading would trigger that, it sounds coincidental because I can't see why it would. I agree, we should probably reset the access key at the same time, but I'd need to dig into the code to see if there's a reason we didn't.
@good-pm commented on GitHub (Jun 1, 2026):
That would be my expectation, too.
I just deleted the accessKey and loaded a new SimpleFIN token. Didn't have to manually create a new accessKey.
@KevinIsMyName commented on GitHub (Jun 1, 2026):
Actually, in the reset SimpleFIN credentials logic, it already sets both the token and then accessKey. However,
ensureSuccessResponse()fails when resetting the token because that endpoint returns 200 with no error which throws the following error on the frontend:This error comes from this line, which then prevents the frontend from proceeding to reset the accessKey. A very naive solution is to parse as
response?.fooinstead ofresponse.foo.@bustedlawnchair commented on GitHub (Jun 3, 2026):
Just wanted to add a data point here. I am getting the same error mentioned earlier
I had SimpleFIN configured then removed both my credentials in AB and the token in SimpleFIN. Now I am unable to link with a new token. I'm not sophisticated enough to make edits in the sqlite database like others have mentioned, but I just wanted to add my experience in the hope a future release will fix the bug.