-
Notifications
You must be signed in to change notification settings - Fork 36
Description
The following is the error that I received while running the example app. Kindly have a look at this:
I/flutter (22356): ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (22356): The following assertion was thrown during a scheduler callback:
I/flutter (22356): setState() called after dispose(): WelcomeScreenState#1f5f4(lifecycle state: defunct, not mounted)
I/flutter (22356): This error happens if you call setState() on a State object for a widget that no longer appears in
I/flutter (22356): the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error
I/flutter (22356): can occur when code calls setState() from a timer or an animation callback. The preferred solution
I/flutter (22356): is to cancel the timer or stop listening to the animation in the dispose() callback. Another
I/flutter (22356): solution is to check the "mounted" property of this object before calling setState() to ensure the
I/flutter (22356): object is still in the tree.
I/flutter (22356): This error might indicate a memory leak if setState() is being called because another object is
I/flutter (22356): retaining a reference to this State object after it has been removed from the tree. To avoid memory
I/flutter (22356): leaks, consider breaking the reference to this object during dispose().
I tried resolving this to some extent using the mounted property of the Widget build however, it still throws the following error:
I/flutter (22356): ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (22356): The following NoSuchMethodError was thrown during a scheduler callback:
I/flutter (22356): The getter 'isLooping' was called on null.
I/flutter (22356): Receiver: null
I/flutter (22356): Tried calling: isLooping