Revert "feat(ios): back gesture with full screen swipe (#705)"

[td-tomasz]

This reverts commit 769a3a2.

Summary

Test Plan

What's required for testing (prerequisites)?

What are the steps to reproduce (after prerequisites)?

Compatibility

OS	Implemented
iOS	✅❌
Android	✅❌

Checklist

• I have tested this on a device and a simulator
• I added the documentation in README.md
• I updated the typed files (TS and Flow)

[zRelux]

769a3a2 made it stop working for me as well with react-native-collapsible-tab-view

[troZee]

@intergalacticspacehighway Can we revert your changes? Maybe we should consider adding this fix #705 (comment)

@td-tomasz-joniec what functionality will be broken, when this patch is removed? Will it introduce some regression?

[intergalacticspacehighway]

@zRelux what has stopped working? Can you please explain the issue?

@troZee reverting can break the back gesture when fullScreenSwipeEnabled is enabled for pop react-navigation. Not a massive breaking change, but I am still unclear on the reason for reverting.

The additional issue asked here is a different feature request to support non-native stack (allow swiping back from the edge when currentPage > 0 and using non-native stack). I can look into that but that won't be solved even if we revert this PR.

[td-tomasz]

@intergalacticspacehighway Can we revert your changes? Maybe we should consider adding this fix #705 (comment)

@td-tomasz-joniec what functionality will be broken, when this patch is removed? Will it introduce some regression?

I am only interested in reverting this change as this code breaks correct touch handling when pager view is inside scrollview

[intergalacticspacehighway]

@td-tomasz-joniec are you facing this #722 issue or is it something else?

[zRelux]

@intergalacticspacehighway swipe back navigation when using react-native-collapsible-tab-view

[intergalacticspacehighway]

@zRelux does reverting the changes fix the issue? Can you confirm if you are using the regular stack from react-navigation and not the native stack navigator?

[zRelux]

Yes I downgraded to 6.1.4 (release before the fix) and it works, I am using stack from expo-router (which I believe is the native one)

[intergalacticspacehighway]

@zRelux can you share a repro? I tried creating one here with the expo router, but not able to reproduce the issue.

Screen.Recording.2023-09-26.at.9.44.55.PM.mov

[troZee]

Can we add this code based on prop called rnsPanGestureRecognizer?

[Anybowdy]

Any update ? still not working for me even on 6.1.4, I'm using @react-navigation non native Stack and react-native-collapsible-tab-view @intergalacticspacehighway

[troZee]

Any update ? still not working for me even on 6.1.4, I'm using @react-navigation non native Stack and react-native-collapsible-tab-view @intergalacticspacehighway

Could you provide a repro? It will definitely speed it up. Right now, I cannot reproduce it

[IN-applaunch]

I'm facing an issue with gesture detection in my React Native project. I'm implementing a custom tab view and also using a pager component. The problem arises because, when using these together, the gesture detection doesn't work as expected. It seems like one gesture handler is overriding or interfering with the others, leading to some gestures not being detected at all. This results in interaction issues, where users can't swipe or interact with the views properly.

The specific problem is that the pager's gesture detection takes priority, which then disables or limits the gestures in my custom tab view. I'm looking for a solution that allows both components to handle gestures independently without conflict, ensuring smooth and expected behavior in my app's UI.