flutter-smell-mounted-checks

To fix setState after an async call in Flutter, you should move the asynchronous work to controllers, cancel timers during disposal, or replace setState with reactive updates to avoid lifecycle defects.

Flutter requires mounted checks before updating the UI because widgets can be disposed during asynchronous gaps, and updating an unmounted widget causes crashes, memory leaks, or inconsistent UI state.

You can detect navigation after async gaps in Flutter by scanning for Navigator calls following await statements, then applying root-cause analysis to move navigation logic or verify context.mounted before proceeding.

The best way to handle widget lifecycle ownership during Flutter async operations is moving async work to controllers, canceling disposal tasks, or replacing setState with reactive updates rather than relying on mounted checks.

You can use context.mounted instead of mounted for async navigation in Flutter, but the preferred approach is moving the navigation logic out of the widget, canceling disposal, or applying reactive updates to eliminate the smell entirely.

Exceptions where mounted checks are acceptable in Flutter development exist, but every accepted exception must be documented and logged to a project artifact during auditing or refactoring to maintain code quality.