Pressable elements not working in native-stack on Android devices with new architecture

[DrZoidberg09]

Current behavior

When using Android devices (iOS and Android emulator is fine) you cannot use onPress in the header bar. onPressIn and onPress out does work. This was tested mostly with Samsung devices.
This only happens with native-stack / Expo Router.
Please have a look here: expo/expo#30032
Further information also in the linked issue in the facebook/react-native repo.

Expected behavior

onPress should work also on physical Android devices.

Reproduction

https://github.com/DrZoidberg09/RN-Android-Touch-Issue/

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• @react-navigation/native-stack
• react-native-tab-view

Environment

• [] I've removed the packages that I don't use

package	version
@react-navigation/native
@react-navigation/bottom-tabs
@react-navigation/drawer
@react-navigation/material-top-tabs
@react-navigation/stack
@react-navigation/native-stack
react-native-safe-area-context
react-native-screens
react-native-gesture-handler
react-native-reanimated
react-native-tab-view
react-native-pager-view
react-native
expo
node
npm or yarn

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native
• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• react-native-tab-view

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[github-actions]

Hey! Thanks for opening the issue. Seems that this issue is related to react-native-screens library which is a dependency of React Navigation. Can you also post your issue in this repo so that it's notified to the maintainers of that library? This will help us fix the issue faster since it's upto the maintainers of that library to investigate it.

[satya164]

software-mansion/react-native-screens#2219

[kriit24]

same thing in ios expo/expo#32927

[mwd-mikeeldredge]

I am having same issue. For pressable buttons I have been able to work around using onPressOut instead of onPress. I am seeking a workaround for React-Native Navigation since back buttons are unresponsive. Is anyone aware of any workarounds for this condition? It doesn't matter if new architecture is enabled or disabled. Popped up as soon as we upgraded to version 52 of the Expo Go SDK.

[janoslc]

Hey!
I'm also experiencing he issue using Expo (new arch enabled) and React Navigation. I did the same workaround by replacing all of the onPress calls to onPressOut which solved the issue for now, but it's something to be addressed.
On iOS it works properly.