-2.4 C
New York
Sunday, February 5, 2023

Flutter error: setState() called after dispose()

This article is about a common error that you might encounter when building apps with Flutter.

The Problem

When working with Flutter, you may face this error:Advertisements

Unhandled Exception: setState() called after dispose()

More information:

Lifecycle state: defunct, not mounted)

This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.

The preferred solution is to cancel the timer or stop listening to the animation in the dispose() callback. Another solution is to check the "mounted" property of this object before calling setState() to ensure the object is still in the tree.

This error might indicate a memory leak if setState() is being called because another object is retaining a reference to this State object after it has been removed from the tree. To avoid memory leaks, consider breaking the reference to this object during dispose().


You may notice that not only one but two solutions are mentioned in the error message.

The first solution is to cancel the timer or stop listening to the animation in the dispose() callback.

AdvertisementsThe second solution is to check the mounted property of the state class of your widget before calling setState(), like this:

if (!mounted) return;

    /* ... */


if (mounted) {
  setState(() {
    /* ... */

Hope this helps.


YouÂ’ve learned how to solve the setState() called after dispose() error in Flutter. Keep the ball rolling and continue exploring more intersting stuff about Flutter by taking a look a the following articles:


You can also check out our Flutter category page or Dart category page for the latest tutorials and examples.

Related Articles


Please enter your comment!
Please enter your name here

Latest Articles