Hi, I'm trying to use the package and it's working OK on Android. But in iOS simulator it only gets en_US locale. I've changed the settings to another languages but no lucky. Even deploying in Release Mode for my iOS device (in Portuguese) it still uses the en locale. Any hint on what should be done?

Here my Flutter Doctor:

[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale en-BR)
    • Flutter version 1.12.13+hotfix.5 at /Users/franklin/Development/flutter
    • Framework revision 27321ebbad (3 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/franklin/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Connected device (2 available)
    • iPhone do Franklin • 8ca28e9db21289c970d810c3625aa017c • ios • iOS 13.3
    • iPhone 11 Pro Max  • 29823942-BC97-4196-B74D-A03C680     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

• No issues found!

And my main.dart

Future main() async {
  final FlutterI18nDelegate flutterI18nDelegate = FlutterI18nDelegate(
    useCountryCode: false, 
    fallbackFile: 'en',
    path: 'assets/flutter_i18n',
  );
  WidgetsFlutterBinding.ensureInitialized();
  await flutterI18nDelegate.load(null);
  SystemChrome.setPreferredOrientations([DeviceOrientation.portraitUp])
      .then((_) {
    runApp(new MyApp(flutterI18nDelegate));
  });
}

class MyApp extends StatelessWidget {
  FlutterI18nDelegate flutterI18nDelegate;

  MyApp(this.flutterI18nDelegate);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        appBarTheme: AppBarTheme(brightness: Brightness.light),
        primaryColor: Colors.white,
        scaffoldBackgroundColor: Colors.white,
        accentColor: kMainBlue,
        primaryTextTheme: TextTheme(
          title: TextStyle(
              fontFamily: 'Inter',
              fontWeight: FontWeight.w700,
              letterSpacing: 1.0),
        ),
      ),
      initialRoute: SplashScreen.id,
      routes: {
        LoginScreen.id: (context) => LoginScreen(),
        RegistrationScreen.id: (context) => RegistrationScreen(),
        HomeScreen.id: (context) => HomeScreen(),
        SplashScreen.id: (context) => SplashScreen(),
      },
      localizationsDelegates: [
        flutterI18nDelegate,
        GlobalMaterialLocalizations.delegate,
        GlobalWidgetsLocalizations.delegate
      ],
    );
  }
}

Thanks!

Hi! Thanks for all your effort with this package! Unfortunately I'm having a problem in my tests with iOS platform. My supported locales in main are 'en' and 'pt' with this delegate: FlutterI18nDelegate(useCountryCode: false, path: 'assets/i18n', fallbackFile: 'en'). I have three situations in my tests:

1. System with only one of those languages selected brings the correct language.
2. System with another language selected brings the correct fallback language.
3. System with English and Portuguese language selected always brings Portuguese. I wish I could bring the default system language, not the region.

Something I notice is that I keep getting a return of 'en_BR' (English as default) if I do print(FlutterI18n.currentLocale(context)); in situation 1, 'es_BR' (Spanish as default) if I'm in situation 2 and 'pt_BR' (English as default but Portuguese available) if I'm in situation 3.

Sorry if I'm doing something wrong, but I read the documentation and could not find anything that could help me.

The method 'getdecodedMap' was called on null.
Receiver: null
Tried calling: getdecodedMap()

this error is invoked everytime when I call the FlutterI18n.translate(context,key) function

Snippet of code:

Error:

Why is the language still not switched after long press the copy and paste pop-up box after the language switch? Why is this? What can I do? thank you!

I just noticed u added fallback key to translate method.

In my case i have around 15 supported languages in my app, and i know that English language/file contains all keys with translations. It would be nice to have fallback language, lets say i have some other language selected instead of English and the key is not found in "French" language file, it could use English translation as default.

like this: FlutterI18n.translate(context, "alert_title", "english")

"english" parameter will be fallback language if key "alert_title" is not found in lets say French language file.

I found that there were two things that would happen.

1. Ios system, zh Chinese. An error will be reported after killing the process and restart the application to translate the first string.
2. Occasionally. Problems can occur when switching to another page. And when you get back, the entire application will be in trouble.

Can it be solved in time?

NoSuchMethodError:The method ‘[]’ was called on null.
Receiver:null
Tried calling:[](“motto”)

When loading a new locale, the translationloader was never told which language to use, which meant it fell back to its 'default' locale. This in turn meant that, for the case of the FileTranslationLoader, it would use the intl package's getSystemLocale to determine locale, instead of using the locale selection flow implemented by the rest of the flutter ecosystem.

This patch fixes it by explicitly updating the translationLoader's locale field with the value passed to the LocalizationsDelegate load function.

First of all, thanks for the great library! I use yaml files and use code from example project. The error I get is:

FlutterError (Unable to load asset: assets/i18n/fr.json)

on line:

await flutterI18nDelegate.load(null);

The reason of this error is this function:

  Future<void> _loadFile(final String fileName) async {
    try {
      decodedMap = await rootBundle
          .loadString('$_basePath/$fileName.json')
          .then((jsonString) => json.decode(jsonString));
    } on FlutterError catch (_) {
      var yamlNode = await rootBundle
          .loadString('$_basePath/$fileName.yaml')
          .then((yamlString) => loadYamlNode(yamlString));
      decodedMap = _convertYaml(yamlNode);
    }
  }

For some reason debugger considers the exception as uncaught and therefore stops program. This is quite annoying. I think a better solution is to let the user specify which file type he uses for translation.

Hi, thanks for your library, I had same problem than #17 #18 #28 #29. I had tried to fix it by using your example in #17 but it's not working. Here is my example, what i done wrong ? I need my main async for local storage initialize. thanks

Hello! I'm using this plugin for some time now. Recently I noticed, that after every hot reload my language falls back to the default english. I reverted the version back to 5.2 with the necessary changes and there it works.

For some reason FlutterI18n.currentLocale(context) always returns en_US on the second call or something.

Can you have a look into it?

Thanks!

Cheers

I am currently seeing crashes where the package cannot resolve the file for my current locale (set phone language to Korean for testing). In these cases, the package should default to the fallback locale.

Hi !

Thanks for this package, its very useful. Could you just update the intl package from 0.17.0 to 0.18.0? This causes conflicts in some projects.

Thank you very much

Hello,

I observe strange behavior for some users logged by FirebaseAuth.instance.currentUser using NetworkFileTranslationLoader. For the first 3 launchs, the behavior is correct, in this case app language set to French by default and FlutterI18n.currentLocale(context)?.languageCode returns fr as well.

But, when this logged user closes and reopens exactly 3 times his app, the app language is changing in English despite FlutterI18n.currentLocale(context)?.languageCode is still returning fr in the language menu.

The forcedLocale is also setted on fr on his launch (thanks to debugs logs I putted) so there is no reason that the app language is suddenly setted to English.

If this user use app version with FileTranslationLoader despite of NetworkFileTranslationLoader (so in local) OR if the user isn't logged in FirebaseAuth, the behavior is always excellent ! Only 2 users are concerned (we have more than 20k active users) and even with cache clearing and resinstalls, this strange behavior is always present, when they are logged, after the third app restarting.. The users doesn't call refresh method before the issue comes.

This is my code implementation, where in this case Platform.localeName.split('_')[0] is returning fr (thanks to debugs logs and when we debug FlutterI18n.currentLocale(context)?.languageCode is setted to fr):

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();

  Locale? locale;
  SharedPreferences.getInstance().then((sharePref) {
    if (sharePref.getString('savedLocale') == null)
      locale = Locale(Platform.localeName.split('_')[0]);
    else
      locale = Locale(sharePref.getString('savedLocale') as String);

    final FlutterI18nDelegate flutterI18nDelegate = FlutterI18nDelegate(
      translationLoader: NetworkFileTranslationLoader(
        useCountryCode: false,
        fallbackFile: 'en',
        forcedLocale: locale,
        baseUri: Uri.https("l-algo-de-paulo-8fb41.appspot.com.storage.googleapis.com", "translations"),
        decodeStrategies: [JsonDecodeStrategy()],
      ),
    );

    runApp(MyApp(flutterI18nDelegate));
  });
}

Then, flutterI18nDelegate is used in MaterialApp.localizationsDelegates like this:

localizationsDelegates: [
        widget.flutterI18nDelegate,
        GlobalWidgetsLocalizations.delegate,
        GlobalMaterialLocalizations.delegate,
        GlobalCupertinoLocalizations.delegate,
]

As I said before, for the most part of users, everything is working well, the problem is only present when the user is logged in FirebaseAuth and using NetworkFileTranslationLoader. If he's logged but using FileTranslationLoader, everything works well. If he's not logged but using NetworkFileTranslationLoader, everythin works well also.

I don't know how could I get more informations to help you to understand this issue better, but not hesitate to ask me something !

Thanks a lot for your plugin and all your work !

Hi, I just completed the PR that enables translation with FlutterI18n instance, and without context. Basically I made BuildContext nullable in 4 functions that required it: translate(..), plural(..), currentLocale(..) and refresh(..). I added an optional named parameter FlutterI18n? instance to all of these, and have added it to I18nText and I18nPlural widgets as well. I decided to go with this kind of implementation to avoid adding additional 4 functions to the FlutterI18n class. IMHO it would make it too bloated. I am not completely satisfied with this solution either, since you need to pass null for BuildContext each time you translate without it, but I didn't have any better ideas how to implement it.

I have added tests as well.

Now you can register a FlutterI18n instance, and call for translator, for instance, somewhere in your data layer, like this:

FlutterI18n instance = GetIt.instance.get();
String translatedText = FlutterI18n.translate(null, 'translation_key', instance: instance);  

Whenever you pass an instance that is not null it will avoid trying to use the context. When instance is not passed context is used. Developers must take care not to set both BuildContext and instance to null.