Error with hot reload about get_it HOT 8 CLOSED

Where do you call your register function? If you do it directly in main before runApp it should not happen.

from get_it.

Sorry, I haven't had noticed you have answered, but yes, that solved my problem. Thanks!

from get_it.

Did this solve your problem?

from get_it.

sorry guys, i am trying to register with context in this case. If i do hot reload getting this error. I need context to register, so i did inside the
build(BuildCotext context){
setsetupLocator(context)
}

so how to do in this case. Thanks

from get_it.

@MuthuHere this is possible, but you'll need some logic to handle it inside your GetIt setup code. Here's an example:

void setUpServiceLocator(BuildContext context) {
  if (getIt.isRegistered<AppLocalizations>()) {//setup was called before, we only re-register what depends on context
    getIt.unregister<AppLocalizations>();
    getIt.registerSingleton<AppLocalizations>(AppLocalizations.of(context));
    return;
  }
getIt.registerSingleton<AppLocalizations>(AppLocalizations.of(context));
//do all your other setup that's independent of context here
}

from get_it.

@MuthuHere don't do this inside a build function. It can be called anytime. Use a StatefulWidget and access the context in didChangeDependency.

What do you want to register that needs a context? Maybe there is a better way to do this.

@josh-ksr don't use the .of to reach something to register in get_it. Instead register Applocalization before you call runApp directly in get_it as it doesn't depend on the context.

from get_it.

@escamoteur I don't think it is possible to use the new flutter localization system without context, at least i haven't found a way to use it without context yet. But sometimes there's the need to access it independent of a view, for example when creating local notifications inside the business logic layer.
That's why i added a builder to the MaterialApp and setup GetIt inside it, seems to work without problems so far even with hot reload. Or is there any problem with this approach that i just haven't seen yet? Here's some example code:

  Widget build(BuildContext context) {
    return MaterialApp(
          builder: (context, widget) {
            setUpServiceLocator(context);
            return FutureBuilder(
                future: getIt.allReady(),
                builder: (BuildContext context, AsyncSnapshot snapshot) {
                  if (snapshot.hasData) {
                    return widget;
                  } else {
                    return Container(color: Colors.white);
                  }
                });
          },
        );
}

from get_it.

yes, that should work fine. I was just looking at the examples here and didn't see why you need the context when creating the AppLocalisation instance.

from get_it.