So in NewTrip() remove MaterialApp since it inherits from the parent. Just return Scaffold. class NewTrip extends StatelessWidget { @override Widget build(BuildContext context) { return Scaffold( body: Text(‘NEW TRIP’), ); } }
Short answer: It’s NOT SAFE to always ignore this warning, even in a Stateless Widget. A workaround in this case is to use the context before the async call. For example, find the Navigator and store it as a variable. This way you are passing the Navigator around, not passing the BuildContext around, like so: … Read more
Most of the time, you’ll have only 2 Navigator. Which means to obtain the nested one, do: Navigator.of(context) And to obtain the root one do: Navigator.of(context, rootNavigator: true) For more complex architecture, the easiest by far is to use GlobalKey (since you’ll never read Navigators during build) final GlobalKey<NavigatorState> key =GlobalKey(); final GlobalKey<NavigatorState> key2 =GlobalKey(); … Read more
This answer will cover both passing data forward and passing data back. Unlike Android Activities and iOS ViewControllers, different screens in Flutter are just widgets. Navigating between them involves creating something called a route and using the Navigator to push and pop the routes on and off the stack. Passing data forward to the next … Read more