setState() called after dispose()

[giantss]

I'm using google_nav_bar: ^5.0.6 and I found this error through Firebase Crashlytics backend.

The error message is as follows:

Fatal Exception: FlutterError
setState() called after dispose(): _GNavState#90a59(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().