You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)
What happened?
I got my SimpleFIN account all setup and added some banks, but, when I go to link an account, it just continues asking me for the token. I enter it and it looks like it saved, but never shows any of my accounts, just re-prompts for the token. I have tried a token reset and tried to link a brand new account with no history, but still no luck.
It also shows that the token is still unclaimed on SimpleFIN.
I have scoured the documentation and issues, but could not find anything about this problem. I turned on the debug mode and don't see any errors, other than a proxy error.
Verified issue does not already exist?
What happened?
I got my SimpleFIN account all setup and added some banks, but, when I go to link an account, it just continues asking me for the token. I enter it and it looks like it saved, but never shows any of my accounts, just re-prompts for the token. I have tried a token reset and tried to link a brand new account with no history, but still no luck.
It also shows that the token is still unclaimed on SimpleFIN.
The expected result is that the token will be claimed and the banks added to SimpleFIN will be shown, as stated in the documentation: https://actualbudget.org/docs/advanced/bank-sync/simplefin
I have scoured the documentation and issues, but could not find anything about this problem. I turned on the debug mode and don't see any errors, other than a proxy error.
The proxy error is already mentioned here: actualbudget/actual-server#392 and referenced in this closed but incomplete pull request actualbudget/actual-server#399.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Linux
The text was updated successfully, but these errors were encountered: