Freezer cannot be used using "ast" locale as primary language on Android, buttons are not working on the first run making impossible to log in. It also generates the a red screen with yellow letters once you log in (when using the debug build):
No MaterialLocalizations found. BottomNavigatorBar widgets require MaterialLocalizations to be provided by a Localizations widget ancestor. The material library uses Localizations to generate messages, labels, and abbreviations. To introduce a MaterialLocalization, either use a MaterialApp at the root of your applications to include them automatically, or add a Localization widget with a MaterialLocalizations delegate.
following error:
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: ════════
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: Warning: This application's locale, ast_ES, is not supported by all of its
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: localization delegates.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: > A MaterialLocalizations delegate that supports the ast_ES locale was not found.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: See https://flutter.dev/tutorials/internationalization/ for more
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: information about configuring an app's locale, supportedLocales,
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: and localizationsDelegates parameters.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: ════════
I would like to know how "uwu" locale deals with this and if there is an easy fix.
Freezer cannot be used using "ast" locale as primary language on Android, buttons are not working on the first run making impossible to log in. It also generates the a red screen with yellow letters once you log in (when using the debug build):
```
No MaterialLocalizations found. BottomNavigatorBar widgets require MaterialLocalizations to be provided by a Localizations widget ancestor. The material library uses Localizations to generate messages, labels, and abbreviations. To introduce a MaterialLocalization, either use a MaterialApp at the root of your applications to include them automatically, or add a Localization widget with a MaterialLocalizations delegate.
```
following error:
```
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: ════════
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: Warning: This application's locale, ast_ES, is not supported by all of its
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: localization delegates.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: > A MaterialLocalizations delegate that supports the ast_ES locale was not found.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: See https://flutter.dev/tutorials/internationalization/ for more
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: information about configuring an app's locale, supportedLocales,
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: and localizationsDelegates parameters.
2021-03-23 00:52:16.038 14624-14652/f.f.freezer I/flutter: ════════
```
Reading more people having this issue, it seems "MaterialLocalizations" only offers a limited set of translations as described here: https://api.flutter.dev/flutter/flutter_localizations/GlobalMaterialLocalizations-class.html. "ckb" locale users have also this issue as it is shown here: https://github.com/flutter/flutter/issues/35103 and the only fix to this is to do https://flutter.dev/docs/development/accessibility-and-localization/internationalization#adding-support-for-a-new-language
I would like to know how "uwu" locale deals with this and if there is an easy fix.
I built the code from the latest changes and the issue is still there. I didn't test this bug on ADV from Android Studio, only from LineageOS. I'll wait for the next stable release.
I built the code from the latest changes and the issue is still there. I didn't test this bug on ADV from Android Studio, only from LineageOS. I'll wait for the next stable release.
After 5 months and a couple of versions, this bug still persists. Setting Asturian locale on LineageOS will make Freezer to misfunction. On the first run, login browser feature will show "cannot connect to server" if web browser is launched through Freezer. If login is successful, using another locale like en_US of course, and ast_es is set back on Android, Freezer will display a nice gray screen.
After 5 months and a couple of versions, this bug still persists. Setting Asturian locale on LineageOS will make Freezer to misfunction. On the first run, login browser feature will show "cannot connect to server" if web browser is launched through Freezer. If login is successful, using another locale like en_US of course, and ast_es is set back on Android, Freezer will display a nice gray screen.
This issue should be reopened, @exttex
Freezer cannot be used using "ast" locale as primary language on Android, buttons are not working on the first run making impossible to log in. It also generates the a red screen with yellow letters once you log in (when using the debug build):
following error:
Reading more people having this issue, it seems "MaterialLocalizations" only offers a limited set of translations as described here: https://api.flutter.dev/flutter/flutter_localizations/GlobalMaterialLocalizations-class.html. "ckb" locale users have also this issue as it is shown here: https://github.com/flutter/flutter/issues/35103 and the only fix to this is to do https://flutter.dev/docs/development/accessibility-and-localization/internationalization#adding-support-for-a-new-language
I would like to know how "uwu" locale deals with this and if there is an easy fix.
I have refactored the language system, ast seems to be working on the latest beta release. Please reopen if the problem presist after release.
I built the code from the latest changes and the issue is still there. I didn't test this bug on ADV from Android Studio, only from LineageOS. I'll wait for the next stable release.
After 5 months and a couple of versions, this bug still persists. Setting Asturian locale on LineageOS will make Freezer to misfunction. On the first run, login browser feature will show "cannot connect to server" if web browser is launched through Freezer. If login is successful, using another locale like en_US of course, and ast_es is set back on Android, Freezer will display a nice gray screen.
This issue should be reopened, @exttex