fix(iOS): Disable interactiveContentPopGestureRecognizer #3141
Conversation
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
t0maboro
approved these changes
Aug 18, 2025
WoLewicki
approved these changes
Aug 18, 2025
kmichalikk
deleted the
@kmichalikk/interactive-content-pop-gesture-disable
branch
kmichalikk
added a commit
that referenced
this pull request
Aug 19, 2025
…in progress (#3142) ## Description This is a followup to #3093 and #3141. We now handle repeatedly clicking back button on iOS 26, and disable interactiveContentPopGestureRecognizer which triggers without fullScreenGesture prop enabled, but it still is possible to click back button and swipe when fullScreenGesture is enabled. One possible solution is to check if transitionCoordinator is set and abort handling the gesture if it is. ## Changes Added check for transitionCoordinator == nil before allowing for gesture to be received. ## Test code and steps to reproduce Use Test3093.
kmichalikk
added a commit
that referenced
this pull request
Sep 23, 2025
## Description Resolves software-mansion/react-native-screens-labs#369, might resolve #3161, reverts #3141, #3142 This PR attempts to enable interactiveContentPopGestureRecognizer for iOS 26 to achieve native screen popping behavior. Until 26, the default was to swipe from the edge of the screen. We had the option to do fullscreen switch, which was controlled by a `fullScreenSwipeEnabled` prop. Since the default behavior has changed, this prop, along with `gestureResponseDistance`, is being ignored from now on. New iOS allows for popping multiple screens almost at once, which we still cannot support due to asynchronous nature of stack updates coming from host to JS that would create a "feedback loop" in situation like the following: host pops 1. screen + sends update, pops 2. screen + sends update -> JS acknowledges 1. update + sends updated state -> host gets 2. screen from JS and pushes it again. This PR attempts to block more than 1 pop at once by removing interactions from the whole screen. As a (desired) side effect, this also disables interactions on the screen below the one that is popped until the transition finishes. ## Changes - removed `RNSPanGestureRecognizer` from iOS 26 build and replace it with native `interactiveContentPopGestureRecognizer` - disabled all interactions when screens are in transition - updated docs ## Test code and steps to reproduce Use Test3173 to test swipe and interactions on bare screens API & compare with any other test that uses react-navigation stack, i.e Test3093. Use Test3093 with additional screenOptions: ```ts { animation: 'slide_from_bottom', animationMatchesGesture: true, } ``` to test custom animations on swipe back. --------- Co-authored-by: Kacper Kafara <kacperkafara@gmail.com>
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
(Duplicated in code comment)
iOS 26 introduces new gesture recognizer which replaces our RNSPanGestureRecognizer. The problem is that we are not able to handle it here for various reasons:
This doesn't prevent from swiping when dismissing with back button is in progress and when fullScreenSwipe is enabled, things still can break. This will be fixed in another PR.
Testing
Use Test3093. Observe no full screen swiping or any unexpected behavior on iOS 26 when the prop is not enabled.