Dart New Added 9 October 2026

Flutter: Looking up a deactivated widget's ancestor is unsafe

Code used a BuildContext after its widget had left the tree, almost always after an await: the user navigated away or the dialog closed, then the callback carried on and called Navigator.of(context) or ScaffoldMessenger.of(context). The context object still exists but has nowhere in the tree to look things up from. It is intermittent because it depends on whether the user leaves before the async work finishes.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

// Check the context is still mounted after every await
Future<void> _save() async {
  await api.save(form);
  if (!context.mounted) return;
  Navigator.of(context).pop();
}

// Or look things up before the await, while the context is valid
final messenger = ScaffoldMessenger.of(context);
await api.save(form);
messenger.showSnackBar(const SnackBar(content: Text('Saved')));

// Inside a dialog, use the dialog builder's context, not the page's

# The use_build_context_synchronously lint finds most of these
dart analyze

How to diagnose Dart errors

Dart errors are dominated by null safety at runtime and version solving at build time. The null-check operator failure (! on a null) is Dart's equivalent of a NullPointerException and almost always means an assumption about initialisation order was wrong. Pub version solving failures are dependency-graph conflicts and are solved by reading the constraint that pub reports as unsatisfiable, not by deleting the lockfile.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Read the full pub get output. It names the two packages whose constraints conflict. Deleting pubspec.lock hides that information without fixing anything.
Replace ! with a null check plus a meaningful error, or with late final where initialisation genuinely happens before first use. The crash location is where the assumption broke.
Run flutter doctor -v before debugging any build failure. It catches missing Android SDK components and licence acceptance, which produce misleading Gradle errors.
Use dart pub deps --style=tree to see the resolved graph and find which transitive dependency is pinning an old version.
Clear derived state with flutter clean only after you have read the error. It resets the symptom and loses the evidence.

Tools worth reaching for

flutter doctor -v
dart pub deps
dart analyze
flutter run --verbose

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

api.flutter.dev dart.dev

Related Dart errors

See all 20 Dart errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.