flutter

This crash means a WidgetRef was used after its widget left the tree, usually in an async callback. Read what you need before the await, then guard with a mounted check.

This crash means you called context.of() after the widget left the tree, usually in an async callback or dispose(). Capture the value before the await, or in didChangeDependencies().

FutureBuilder re-runs your async work every time the parent rebuilds because you created the Future inside build. Hoist it into State.initState (or memoize it), and FutureBuilder will reuse the same Future. Here is the why, the repro, and every variant that bites.

Dart 3.12 adds an experimental primary constructors syntax that declares fields and a constructor in the class header, collapsing the classic three-line data class to one.

Pick Riverpod for most new Flutter apps in 2026. Choose Bloc for large teams that want an enforced event-driven structure, and keep Provider only for legacy code.

RenderBox was not laid out is almost always a secondary error. Find the first layout assertion above it, usually a scrollable given unbounded constraints, and fix that.

This crash means code touched a controller after dispose() ran. Guard async callbacks with a mounted check, and never dispose a controller you do not own.

This error means you mutated state while Flutter was building. Move the setState out of build, or defer it with addPostFrameCallback. Here is why it happens and the right fix.

Render loading, data, and error UI from a single AsyncValue in Riverpod 3. Use AsyncNotifier and AsyncValue.guard for mutations, .when() and switch pattern matching for the UI, keep previous data on refresh, and migrate the legacy StateNotifier pattern. Tested on flutter_riverpod 3.x, Flutter 3.44, Dart 3.x.

AnimationController, TextEditingController, and ScrollController hold resources that Dart's GC cannot reclaim until you dispose them. Here is the correct pattern, the ordering rules, and how to catch leaks before they ship.