"new architecture" touch is very inconsistent for TextInput and Button (both RN and Paper) #4517
Description
Current behaviour
I'm starting a mobile app for my company and am using expo v51, react-native v75, react-navigation (v7 rc), and react-native-paper v5. I turned "new architecture" on because I'm just starting and I want to smoothly switch to RN 76 when it comes out by verifying that I'm not doing anything that would not work with new architecture. I noticed in my eas preview builds that on real android phones I couldn't even press buttons or bring up the keyboard in text input. It all works fine an ios phones and emulators and simulators.
I turned off "new architecture" and android phones work fine. I'm worried that with RN 76 already hitting RC that this problem hasn't been solved yet.
I built up a minimal repo and things worked fine until adding in react-navigation.
I had posted on expo and someone there actually debugged and found this:
"this looks like an interaction between react-native-screens and react-native-paper's button component. i investigated this a bit and traced it back to this single line:
if you comment that out, it fixes all other touches"
Expected behaviour
How to reproduce?
Minimal repo: https://github.com/kferch-teamworks/RNAndroidTouch
Preview
What have you tried so far?
Your Environment
| software | version |
|---|---|
| ios | x |
| android | x |
| react-native | x.x.x |
| react-native-paper | x.x.x |
| node | x.x.x |
| npm or yarn | x.x.x |
| expo sdk | x.x.x |