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
Just linked Authentic with Actual and the initial user is working fine. Went to add another user and got this error: -
Error getting users An internal error occurred, sorry! Visit https://actualbudget.org/contact/ for support. (ref: Failed to parse response: JSON Parse error: Unexpected identifier "Too")
I still added the new User which worked okay.
But... When I log in as that new User, it asks them to create a budget or import. Not sure if this is related to the bug or is the way out is designed. I thought they would be able to share my budgets ???
How can we reproduce the issue?
Connect Authentik, enable Multi-User in Actual, Log-in for the first time to take ownership. Go into User Management and error appears.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered:
Verified issue does not already exist?
What happened?
Just linked Authentic with Actual and the initial user is working fine. Went to add another user and got this error: -
Error getting users An internal error occurred, sorry! Visit https://actualbudget.org/contact/ for support. (ref: Failed to parse response: JSON Parse error: Unexpected identifier "Too")
I still added the new User which worked okay.
But... When I log in as that new User, it asks them to create a budget or import. Not sure if this is related to the bug or is the way out is designed. I thought they would be able to share my budgets ???
How can we reproduce the issue?
Connect Authentik, enable Multi-User in Actual, Log-in for the first time to take ownership. Go into User Management and error appears.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: