Skip to content

fix: 🐛 Prevent re-entrant calls to _onComplete during rapid barri…#646

Closed
apizon wants to merge 3 commits into
SimformSolutionsPvtLtd:masterfrom
apizon:master
Closed

fix: 🐛 Prevent re-entrant calls to _onComplete during rapid barri…#646
apizon wants to merge 3 commits into
SimformSolutionsPvtLtd:masterfrom
apizon:master

Conversation

@apizon

@apizon apizon commented May 4, 2026

Copy link
Copy Markdown
Contributor

Description

Add _isCompleting boolean guard to prevent concurrent execution of _onComplete()
when rapid barrier taps occur during step transition animations. This prevents
null-check crashes from calling reverse() on already-disposed AnimationControllers.

Fixes crash when user rapidly taps the barrier during showcase step transitions (#645).
Tested if on my app and can confirm I now longer see any assertion failures or unhandled exceptions.

Checklist

  • The title of my PR starts with a [Conventional Commit] prefix (fix:, feat:, docs: etc).
  • I have followed the [Contributor Guide] when preparing my PR.
  • I have updated/added relevant dartdoc comments with ///.

Breaking Change?

  • Yes, this PR is a breaking change.
  • No, this PR is not a breaking change.

Related Issues

Fixes #645

…aps (SimformSolutionsPvtLtd#645)

Add _isCompleting boolean guard to prevent concurrent execution of
_onComplete()
when rapid barrier taps occur during step transition animations. This
prevents
null-check crashes from calling reverse() on already-disposed
AnimationControllers.

Fixes crash when user rapidly taps the barrier during showcase step
transitions.
@vasu-nageshri-simform

Copy link
Copy Markdown
Contributor

Hello @apizon,

I was able to reproduce the same issue using the code you provided. Could you please take a look and confirm?

For reference, I've attached a video demonstrating the problem. Thank you!

Screen.Recording.2026-06-11.at.11.07.29.AM.mov

@apizon

apizon commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Hi @vasu-nageshri,

It looks like the PR is not fixing the issue indeed, at least not when using programmatic auto-spam... (also tried it on my end with same result as you)
When used with manual click spam on my app I noticed the issue did not appear anymore after this PR but maybe I just got lucky, or maybe the issue is not exactly the same when doing barrier taps vs programmatic ones.

Anyway, I'm affraid I'm out of ideas for this one, I've reverted to 4.0 in the meantime since it works with no issue on my app.

@vasu-nageshri-simform

Copy link
Copy Markdown
Contributor

Close, as it has been resolved in #654

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unhandled exception when rapidly tapping during showcase

3 participants