Flutter says the context does not include a Navigator
Navigator operation requested with a context that does not include a Navigator.Short answer
Navigator.of looks upward from the context you pass. If that context belongs to a widget above the Navigator, usually the widget that builds MaterialApp itself, nothing is found and Flutter throws. Use a context from a widget below MaterialApp, for example through a Builder, or navigate with a navigatorKey.
Fix it fast
1Find out which cause you have
Find the line that calls Navigator.of or Navigator.push and note which build method its context comes from. If that method also returns MaterialApp or CupertinoApp, you have the cause.
grep -rn "Navigator\.\(of\|push\|pop\)" lib/ | head -202Match what you see, then jump to its fix
What does the error look like?
Navigator operation requested with a context that does not include a Navigator.The context used to push or pop routes from the Navigator must be that of a widget that is a descendant of a Navigator widget.
Cause 1 of 2
The context comes from the widget that builds MaterialApp
1Check
Navigator.of returns the closest Navigator above the context. The Navigator is created inside MaterialApp, so a context from the widget that creates MaterialApp is above it and finds none.
grep -rn "MaterialApp" lib/2Fix
Move the code that navigates into a widget below MaterialApp, such as a separate screen widget. If you want to keep it inline, wrap it in a Builder: it adds one more element and gives you a context from below.
home: Builder(
builder: (context) => TextButton(
onPressed: () => Navigator.of(context).push(
MaterialPageRoute(builder: (_) => const NextPage()),
),
child: const Text('Next'),
),
),3Verify
Tap the button; the new route opens and the error is gone.
flutter runConfirmed by api.flutter.dev
Cause 2 of 2
The code runs where no BuildContext exists
1Check
Navigator.of needs a context that sits below a Navigator. Code outside the widget tree has none to give it.
grep -rn "navigatorKey" lib/2Fix
Give MaterialApp a GlobalKey<NavigatorState> and navigate through its currentState. The key replaces the context lookup.
final navigatorKey = GlobalKey<NavigatorState>();
MaterialApp(
navigatorKey: navigatorKey,
home: const HomePage(),
);
// anywhere in the app
navigatorKey.currentState?.pushNamed('/details');3Verify
Trigger the navigation from the service and check that the route opens.
flutter runConfirmed by api.flutter.dev
How do I stop it coming back?
- Put each screen in its own widget class so its context is always below MaterialApp.
- Keep one navigatorKey in a single file when non-widget code must navigate.
- Do not change the navigatorKey at runtime: a new key builds a new Navigator and loses the app state.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
- SessionBirdAn omnichannel engagement suite in Flutter: campaigns, chatbot, tickets, analytics and live calling.
Related fixes
Mobile apps
AudioCache has no play method after updating audioplayers
The method 'play' isn't defined for the type 'AudioCache'.
Since audioplayers 1.0, AudioCache only turns asset files into local files and caches them.
2 causes, each with a fixMobile apps
Flutter Bloc throws that emit was called after the event handler completed
emit was called after an event handler completed normally.
Each on<Event> handler gets its own Emitter, and it stops working the moment the handler's returned Future completes.
2 causes, each with a fixMobile apps
analysis_options.yaml: the URI it includes can't be found
include_file_not_found
The analyzer reports include_file_not_found when the file named after include: in analysis_options.yaml does not resolve.
2 causes, each with a fixMobile apps
Dart error: the body might complete normally and return null for a non-nullable type
body_might_complete_normally
Dart found a path through your function or callback that reaches the closing brace without a return.
3 causes, each with a fixMobile apps
Dart throws ConcurrentModificationError while looping over a list
ConcurrentModificationError
Dart throws this when a collection changes size while something iterates it.
2 causes, each with a fixMobile apps
Dart cannot turn a compact timestamp like 20201101153000 into a DateTime
FormatException: Invalid date format
DateTime.parse accepts a subset of ISO 8601, and a time part must be introduced by T or a space.
2 causes, each with a fix