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 have two Android devices. One is configured in English and another in Spanish. In the first ActualBudget runs perfectly. But in the second, all fields are translated. Even payees and account names are translated, what causes weird issues.
When trying to split a movement, remaining unassigned amount does not get updated. After setting the actual remaining value in a second split, app shows a fatal error and split data is not updated.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Mobile Device
The text was updated successfully, but these errors were encountered:
That sounds like it's the device, not Actual, doing the translation. Translation support has only recently been added (in edge, not release) and it wouldn't translate account names and payee names
Does anything show when you click "show error" when the fatal error comes up?
Yes, most probably is chrome WebView doing the translation by itself. I opened Actual Budget in regular browser and disabled translation for its subdomain. This setting affects the progressive app, so now it is in English, but it works.
Verified issue does not already exist?
What happened?
I have two Android devices. One is configured in English and another in Spanish. In the first ActualBudget runs perfectly. But in the second, all fields are translated. Even payees and account names are translated, what causes weird issues.
When trying to split a movement, remaining unassigned amount does not get updated. After setting the actual remaining value in a second split, app shows a fatal error and split data is not updated.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Mobile Device
The text was updated successfully, but these errors were encountered: