[Due for payment 2026-04-14] [Due for payment 2026-04-07] [$375] Android: Investigate and fix onPress not working for Pressable in Tooltip

[ishpaul777]

Coming from #59577

We are encountering an Android-specific (reproducible on certain Samsung models) issue where the onPress event does not triggered for Pressable components when used inside a Tooltip. As a temporary workaround, we’ve replaced onPress with onPressIn, which works but is not an ideal solution.

This issue needs further investigation to identify the root cause and implement a proper fix that allows onPress to work reliably within Tooltip on Android devices.

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022029971611969626753
• Upwork Job ID: 2029971611969626753
• Last Price Increase: 2026-03-14

[melvin-bot]

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[utkershrajvenshi]

@ishpaul777 this issue indicates that the behaviour of Pressables in react-native is flaky on real devices, Android and iOS both. This comment indicates it occurs when we use react-native-gesture-handler above in view hierarchy, and it's API ends up cancelling the Pressable events from RN. This comment suggests using the Pressable component from react-native-gesture-handler instead of react-native as it (seemingly) solves this problem. (I haven't been able to reproduce this on my device to verify the claim)

[mallenexpensify]

Starting at LOW status cuz of

This issue needs further investigation to identify the root cause and implement a proper fix that allows onPress to work reliably within Tooltip on Android devices.

Please bump up and/or tag me if you feel it's needed.

[ishpaul777]

@utkershrajvenshi Thanks for your investigation.

This software-mansion/react-native-screens#2219 (comment) suggests using the Pressable component from react-native-gesture-handler instead of react-native as it (seemingly) solves this problem

while this may solve the problem I think its still a workaround, it would be great if we could solve this upstream without any further workaround

[melvin-bot]

@sonialiap, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[sonialiap]

@ishpaul777 any updates? Anything I can assist with?