AvoidContextAfterAwaitInStaticRule class

Quick fix that inserts if (!mounted) return; before context usage. Warns when BuildContext is used after await in async static methods.

Since: v2.4.0 | Updated: v4.13.0 | Rule version: v4

Alias: context_after_await_static, async_static_context_danger

This is the most dangerous pattern: after an await, the widget may have been disposed, making the context invalid. Using it will crash the app.

Recognized Mounted Guards

The rule recognizes context.mounted guards and won't report false positives when context is properly guarded:

if (!context.mounted) return;        // Early exit guard
if (context.mounted == false) return; // Explicit comparison
if (context.mounted) { ... }          // Positive block guard
if (context.mounted && other) { ... } // Compound conditions
context.mounted ? context : null      // Guarded ternary

See also:

• AvoidContextInAsyncStaticRule for any async static with context
• AvoidContextInStaticMethodsRule for any static with context

BAD - Context used after await (CRASH RISK!):

class MyHelper {
  static Future<void> fetchAndShow(BuildContext context) async {
    final data = await fetchData();  // Widget may dispose during await
    ScaffoldMessenger.of(context).showSnackBar(...);  // CRASH!
  }
}

GOOD - Check mounted before using context:

static Future<void> fetchAndShow(BuildContext context) async {
  final data = await fetchData();
  if (!context.mounted) return;  // Guard protects subsequent code
  ScaffoldMessenger.of(context).showSnackBar(...);  // Safe!
}

ALSO GOOD - Use callback or navigator key:

// Option 1: Pass mounted check callback
static Future<void> fetchAndShow(
  BuildContext context,
  bool Function() isMounted,
) async {
  final data = await fetchData();
  if (!isMounted()) return;
  ScaffoldMessenger.of(context).showSnackBar(...);
}

// Option 2: Use navigator key (no context needed)
static Future<void> fetchAndShow() async {
  final data = await fetchData();
  navigatorKey.currentState?.showSnackBar(...);
}