App is blank when language is not available

[cuhsy]

First launch, app is blank, all I can see is a white screen. Tried reinstalling, clearing data, installing older versions (down to 2.21.1) and no luck. Tried both F-droid and GitHub releases. Thought of manually giving it file permissions, but the app was nowhere to be found in any permission settings at all.

Nothing phone 4a pro, arm64, Android 16, let me know if any other details are needed

[Demizo]

Oh no! Are you using an external folder? My first thought is that something got corrupted preventing the launch, but clearing the storage data or reinstalling would have fixed that. Could you share the Android app logs from when you attempt to launch?

[cuhsy]

Found the issue! This is a first time launch, but I found this in the log:

error AppLocalizations.delegate failed to load unsupported locale "el_GR". This is likely an issue with the localizations generation tool.

Unhandled Exception: AppLocalizations.delegate failed to load unsupported locale "el_GR"

It's having issues loading in English because my phone is in Greek, which is odd because my old phone, which was also in Greek, had no problem running the app.

I changed my device language to English, and the app loaded perfectly fine. I changed the app language to English, changed my phone language back to Greek, and now there is no problem anymore. So I'm assuming Greek is not the only language that has this problem and a fallback to English must be implemented. I will attach the entire log of the app not loading first time launch, in case there's anything of use for you.

dy08_06-07-35-07_540.log

[Demizo]

Good catch! It definitely should be falling back when the current language is not supported.

[Demizo]

I wasn't able to reproduce this on my device or in am emulator, so it may be an OS specific issue. Regardless, I have added a potential fix to the next update to set a more explicit fallback. If you get the chance to try it on the next update that would be appreciated!

[Demizo]

@cuhsy Following back up on this, did you get the chance to try this in v2.24.1? If so, was the issue resolved?