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
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
Setting LC_ALL=C does not show the initial warning but does show the stack trace and the apps comes up with the same missing content. I've both building a snap and running normally. Note that when running a build outside of a snap I also get this message:
flutter: Observatory listening on http://127.0.0.1:46837/x3c7L1b7bIs=/
flutter: ════════
flutter: Warning: This application's locale, C, is not supported by all of its
flutter: localization delegates.
flutter: > A GalleryLocalizations delegate that supports the C locale was not found.
flutter: > A MaterialLocalizations delegate that supports the C locale was not found.
flutter: See https://flutter.dev/tutorials/internationalization/ for more
flutter: information about configuring an app's locale, supportedLocales,
flutter: and localizationsDelegates parameters.
flutter: ════════
flutter:
The text was updated successfully, but these errors were encountered:
Interesting -- I'm not very familiar with Linux development, but from really quickly looking StackExchange, it seems like LC_ALL=C basically sets up all applications to use the default locale.
However, if that's the case, then it seems like the Flutter framework is doing the wrong thing and passing up that constant C instead of the supposed default locale. If that's the case, would it be possible to pass up the value of what the default locale is instead of just C into the framework?
On Linux, when the
LC_ALL
environment variable is set to something unexpected it falls back to locale 'C'However, it then prints a long stack trace:
Stack trace
...and fails to draw much of anything:
Setting
LC_ALL=C
does not show the initial warning but does show the stack trace and the apps comes up with the same missing content. I've both building a snap and running normally. Note that when running a build outside of a snap I also get this message:The text was updated successfully, but these errors were encountered: