[iOS] Move Tap cancelation to dispatch_after#4280
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes an iOS-specific timing issue where Tap gesture failure/finalization could be delayed during UIScrollView drag/deceleration by replacing performSelector:...afterDelay: timers (default run-loop mode) with cancellable dispatch_after blocks (main queue), ensuring timers fire even in UITrackingRunLoopMode.
Changes:
- Added cancellable
dispatch_after-based scheduling for tap cancel/failure timers. - Replaced
cancelPreviousPerformRequestsWithTarget:selector:with explicit cancellation of pending GCD blocks. - Added internal tracking for pending cancellations to allow cleanup/reset.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes #3471
On iOS, in a multi-gesture setup (e.g. an
Exclusivesingle-tap / double-tap combination), atap'sonDeactivate/onFinalizewas delayed until aScrollView/FlatListfinished its drag or momentum scroll.onBeginfired immediately, but the single tap never runonActivate/onEnd— it stayed in the began state and finalized as failed only once scrolling settled.RNBetterTapGestureRecognizerarmed itsmaxDurationandmaxDelayfailure timers withperformSelector:withObject:afterDelay:, which schedules anNSTimerinNSDefaultRunLoopModeonly. While aUIScrollViewis dragging or decelerating, the main run loop runs inUITrackingRunLoopMode, so those timers are starved until the scroll stops.To fix this, I replaced the two
performSelector:…afterDelay:calls with cancellabledispatch_afterblocks which fire regardless of run-loop mode (it is also consistent with currentLongPress/Flinglogic).Test plan
Tested on the following code: