Repository navigation
Description
Description
To make a separate issue of:
#36710 (comment)
It's been like 1 year there is many issues reported on Android about onPress not fired (in issues of this repo and by a lot of end-user).
Since I cannot reproduce because a lot of this issue are "random", I was looking for an alternative with an onPressOut workaround.
Was able to implement a full working workaround on iOS (scroll management, hitslop, ...) but when switching to Android everything was broke. My solution was based on locationY and locationX but after investigation, I noticed that the value of locationY and locationX on Android is not correct.
For exemple, when the onPressOut is triggered because the touch goes out of the screen, the locationY is equal to pageY.
When the onPressOut is trigger after the touch leave the Pressable, but still on another Pressable (stacked Button for exemple). The locationY looks like it's the value inside the second Pressable (expected 80, but received 15 for exemple).
Impact Touchables (WithoutFeedBack, Opacity, ...).
I don't know if it's the root-cause of all onPress issue, but might not help to handle it correctly.
In the code, found out that there is a "Legacy" / "non-legacy" logic that might explain why it's only on new-arch.
Regards
Steps to reproduce
- Create two Pressable with
onPressOut, log thelocationXandlocationY - Start pressing the first Pressable the slide quickly to the second one.
- The
onPressOutof the first one is triggered but display invalid valuelocationX/Y(supposed to be the calculated values of the second Pressable).
React Native Version
0.80.2
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 15.6
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 13.99 GB / 64.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.16.0
path: ~/.nvm/versions/node/v22.16.0/bin/node
Yarn:
version: 1.22.17
path: ~/.yarn/bin/yarn
npm:
version: 11.5.1
path: ~/.nvm/versions/node/v22.16.0/bin/npm
Watchman:
version: 2025.07.14.00
path: /usr/local/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.5
- iOS 18.5
- macOS 15.5
- tvOS 18.5
- visionOS 2.5
- watchOS 11.5
Android SDK: Not Found
IDEs:
Android Studio: 2025.1 AI-251.26094.121.2512.13930704
Xcode:
version: 16.4/16F6
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.1
path: /usr/local/opt/bin/javac
Ruby:
version: 3.4.5
path: /usr/local/opt/ruby/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 19.1.1
wanted: ^19.1.0
react:
installed: 19.1.0
wanted: 19.1.0
react-native:
installed: 0.80.2
wanted: ^0.80.1
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
See console.log of reproducer / video
MANDATORY Reproducer
https://github.com/Dallas62/rn-pressabe-issue-location
Activity
alwaysRemember commentedon Jan 6, 2026
Has anyone encountered the problem that when using react-native Pressable, the onPress event cannot be triggered by clicking after the application has been running for some time, and it can only be triggered by clicking the far right of the Pressable component?
mcanikhilprajapati commentedon Jan 8, 2026
Issue: onPress not triggering consistently on Google Pixel 7 (Android 16)
Environment
React Native: 0.83.x
Platform: Android
Device affected: Google Pixel 7
Android version: Android 16 (Build 36.1 – latest)
Other devices tested:
Android (older versions/devices): ✅ Works fine
iOS (multiple devices): ✅ Works fine
Description
In a newly created React Native 0.83 app, Touchable* / Pressable onPress events do not trigger consistently on Google Pixel 7.
Sometimes onPress works
Sometimes it does not trigger on first tap
No crash, no error logs
Happens intermittently
Reproducible only on Pixel 7 (Android 16)
Same build behaves correctly on:
Other Android devices (older OS versions)
All tested iOS devices
Expected Behavior
onPress should trigger reliably on every tap.
Actual Behavior
onPress randomly fails to trigger, especially on the first interaction.
Components Tested
TouchableOpacity
TouchableWithoutFeedback
Pressable
Issue observed across all of them.
Additional Notes
App is newly built, not upgraded from older RN versions
No custom gesture handlers involved
No overlapping views intentionally blocking touch
Happens in multiple screens/components
Feels related to Android 16 / Pixel-specific touch handling
Question
Is this a known issue with Android 16 / Pixel devices or with RN 0.83 touch system?
Any recommended workaround or config change to improve touch reliability on Pixel devices?
mcanikhilprajapati commentedon Jan 9, 2026
import pressable from react-native-gesture-handler works fine for all device
alwaysRemember commentedon Jan 9, 2026
I also tried to use react-native-gesture-handler, but I found that after running for a period of time, the button was completely unclickable, and the application had to be restarted.
mcanikhilprajapati commentedon Jan 27, 2026
any update on this issue?
react-native-bot commentedon Jul 28, 2026
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
MaxiAschenbrenner commentedon Jul 28, 2026
still happening for us
mcanikhilprajapati commentedon Jul 29, 2026
After android 15+. this issue created and even after 1 year its not fixed