onPress action on Pressable component inside another triggers both actions

[TomCorvus]

Description

Hello,

I have some Pressable components inside another, and when I click on child one, it's triggered parent onPress action.
It occurs on real and simulator devices on Android and iOS.

Switch with Pressable component from react-native and the child onPress action doesn't trigger the parent onPress action.

I tried others pressable components like TouchableOpacity and here the results when I click on child pressable component:
TouchableHighlight in TouchableOpacity -> both trigered
TouchableOpacity in TouchableHighlight -> parent action trigered
TouchableOpacity in TouchableOpacity -> child action trigered
TouchableHighlight in TouchableHighlight -> child action trigered
Pressable in TouchableHighlight -> child action trigered
Pressable in TouchableOpacity -> both trigered
Pressable in Pressable -> both trigered
TouchableHighlight in Pressable -> both trigered
TouchableOpacity in Pressable -> parent action trigered
TextInput in Pressable -> parent action trigered (only on Android)

Steps to reproduce

1. Clone repo
2. react-native start
3. Click on button on the first tab
4. Check console logs

Snack or a link to a repository

https://github.com/TomCorvus/RNavigation

Gesture Handler version

2.21.2

React Native version

0.76.3

Platforms

Android, iOS

JavaScript runtime

Hermes

Workflow

Expo bare workflow

Architecture

Fabric (New Architecture)

Build type

Debug mode

Device

iOS simulator

Device model

Pixel 7 Pro, iPhone 16 Pro

Acknowledgements

Yes

[TomCorvus]

I can add TextInput in Pressable. When I focus the TextInput, it's trigered the onPress action of Pressable component.
It's seems to occur only on Android. Not on iOS.

[TomCorvus]

I tried your fix, but it seems to not fix the TextInput inside Pressable.

[coado]

I tried your fix, but it seems to not fix the TextInput inside Pressable.

Previous PR fixed different issue. Could you check if #3295 solves this one for you?

[TomCorvus]

Great @coado, it seems to fix the problem. Do you know when a new version including all theses fixes will be released?

[coado]

Great @coado, it seems to fix the problem. Do you know when a new version including all theses fixes will be released?

The stable version will be released around 10th January 2025 probably. The PR is not fully ready to be merged though as it still doesn't work on the old arch :/

[freeboub]

unfortunately, This patch is not enough on my side (with new arch)...
I am in this configuration: Pressable in Pressable -> both trigered
I tried to clone main branch and integrate linked pull request.

[coado]

unfortunately, This patch is not enough on my side (with new arch)... I am in this configuration: Pressable in Pressable -> both trigered I tried to clone main branch and integrate linked pull request.

Hey @freeboub, could you share the code that doesn't work for you? Also, have you tested on this PR specifically?

[freeboub]

Sorry for the delayed answer @coado.
As I workaround the issue in my product, I don't have sure way to reproduce the issue now. And Yes I manually backport this PR in my local repo, but maybe I didn't something wrong. If I find another use case, I will create a small repo for reproduction.
Thank you

[TomCorvus]

@coado do you know when your PR will be merged?
Thank you