Set State is being called after disposed from Animation/Timer callback

[shaurya-src]

On changing the state of the screen with PinCodeTextField, this error is being thrown:

======== Exception caught by foundation library ====================================================
The following assertion was thrown while dispatching notifications for FocusNode:
setState() called after dispose(): _PinCodeTextFieldState#28fbb(lifecycle state: defunct, not mounted, tickers: tracking 0 tickers)

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

[bambinoua]

It looks like this issue was fixed but version is not updated on pub.dev.

[bambinoua]

@adar2378 please update the version on pub.dev.

[esentis]

Do we have an ETA for the update ? :)

[subzero911]

+1, need this fix

I currently have the similar error, when I show and hide the pin field while requesting the focus:

and mounted checking should solve it

[bambinoua]

For now the only "fix" is:

dependency_overrides:
  pin_code_fields:
    git:
      url: https://github.com/adar2378/pin_code_fields.git
      ref: master

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[esentis]

This is still not updated.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[esentis]

Commenting for activity. The issue is still here.

[subzero911]

Seems like an author had abandoned this package... Is anyone here who's willing to fork it and continue supporting?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bambinoua]

@adar2378 we hope the new 8.0.1 version had fixed this issue? :)

[adar2378]

@subzero911 I have not abandoned it. I am looking for maintainers if someone is interested because I have been busy with life and can not find enough time to implement/fix things quickly enough.

@bambinoua Yes, 8.0.1 should fix it.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.