Flutter error: setState() called after dispose()

Last updated on November 6, 2020 The Shadow Loading... 5 comments

Problem

When working with Flutter, you may face this error:

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().

Solutions

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.

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

if (!mounted) return;

setState(){
    /** **/
}

Or:

if (mounted) {
  setState(() {
    /** **/
  });
}

Hope this helps 🙂

Related Articles

Subscribe
Notify of
guest
5 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Isaiah
Isaiah
3 months ago

It helped me thank you brother!

,iuz
,iuz
2 months ago

Thank you!

Atharv
Atharv
27 days ago

thank you

Shrey
Shrey
14 days ago

Thanks a lot.

Achini Amandila
Achini Amandila
12 days ago

It helped me thank you so much brother!

5
0
Would love your thoughts, please comment.x
()
x