search

RayLeaf-Studios / PocketPlan

A simplistic Android app, designed to take care of everyday tasks.
MIT License
119 stars 8 forks source link

Language bug #25

Closed BluePixel4k closed 2 years ago

BluePixel4k commented 2 years ago

There is a language bug. If the system language is English and you change the app language to German (Settings > General > Language > German). Than you add an item to the shopping list, the suggestions are right, but the category is in English, not in German.

Screenshot_Bread

mvnowak commented 2 years ago

So far I could not reproduce your bug (see video), can you be more specific? You said change the app language to German but your screenshot shows only english strings (e.g. the "No important tasks" in the background and the "Add" and "Cancel" button etc.), is this what your app looked like once you selected "german"?

https://user-images.githubusercontent.com/51212295/152588612-ff074736-e70c-40b2-b93c-b1d07068cb48.mp4

BluePixel4k commented 2 years ago

Strange, I have the same settings. But for me, the app does not properly jump over to German. The option "Reset all settings to default" also has no effect on the set language.

Screenshot_20220204-202930

Screenshot_20220204-202950

Screenshot_20220204-203256

mvnowak commented 2 years ago

Thats really odd, does this problem still remain when you exit the app, close it completely and restart it? Also what device / android version are you on?

BluePixel4k commented 2 years ago

Yes, the problem still remains. I just reset the app again as well, but to no avail.

Device: Google Pixel 5 OS: Android 12 - GrapheneOS

mvnowak commented 2 years ago

You were right, this is an initialization bug that we already fixed on the Beta branch in this commit lines 191-194 I just forgot about it, thanks for letting us know tho, it should be fixed in 1.4, if not let us know

mvnowak commented 2 years ago

I found the source of this bug now, it had something to do with how gradle handles multiple languages. The bug fix is included in Release 1.3.3 which should go live in a few hours, once you update your app, please let us know if the problem is resolved.

BluePixel4k commented 2 years ago

Thanks, with the v1.3.3 the bug is now solved.