WebOct 24, 2024 · When I open a chat page as a pop up the initState gets called the first time, but when I use Navigator.pop (context) and then open the chat page again the initState does not get called and I get an error for my StreamSubscription -> The method 'cancel' was called on null. But I do initialize it in the initState. WebMar 25, 2024 · 513 4 10 1 "The thing is, all the state variables are initialized using the setState () method inside the initState ()". You don't need that. If you're in initState, your build should not have happened yet, so just set the state vars. No need to call setState... that will trigger a new build (), and maybe that's what you're seeing.
flutter - 在 null 上調用了 getter
WebOct 16, 2024 · It is best to use the @override void didChangeDependencies () method of the State class. From the docs This method is also called immediately after initState. It is safe to call BuildContext.inheritFromWidgetOfExactType from this method. But make sure to check if you have already performed your initialization WebApr 19, 2024 · In your onGenerateRoute you call the WeatherView constructor each time: case WeatherView.routeName: return const WeatherView (); This in turn will call initState. What you need to do is create the WeatherView page widget once and use it in the onGenerateRoute: final _weatherView = const WeatherView (); In your onGenerateRoute: can i have two hsa
flutter - initState() method is not being called when widget reloads ...
WebMay 22, 2024 · This method is also called immediately after initState. It is safe to call BuildContext.dependOnInheritedWidgetOfExactType from this method. It's also mentioned in your error code initialization based on inherited widgets can be placed in the didChangeDependencies is called after initState and whenever the dependencies … WebOct 15, 2024 · initState called up by default whenever a new stateful widget is added into a widget tree. Now the super.initState performs the default implementation of the base class of your widget.If you call anything before super.initState that depends on the base class then this might cause problem. WebMay 28, 2024 · 1. Yes, you can move that call to deactivate () instead of dispose () since it will be called immediately. I've updated my answer accordingly. – Miguel Ruivo. May 28, 2024 at 22:57. Unfortunately, deactivate () is still called after next widget's initState () – Ferda Nahit FIDANCI. May 28, 2024 at 23:18. can i have two homes