Victor Rothberg Gimael

> > @jugshaurya I can confirm I'm having the same issue, using 71.10, android. It basically makes the new architecture unusable on Android, unless you plan to have no animation....

Also can't get it work anymore, and I've been able to use it in the same project in the past - very strange

Hi @necolas thanks for the feedback, however you really should not close this issue..... other users have mentioned similar problems, please do not ignore this issue just because it happens...

Hmm I am not using the new architecture though, and this problem seems to have happened for a long time (before new architecture existed). We tried this example on our...

We are experiencing this problem in some of our other apps too, this time with no map component mounted whatsoever (disproving my theory above). User is unable to interact with...

Hi @horne3754sg, we have already tried it and the same problem still happens. We were unable to tell whether it makes any different, but it doesn't seem like it. We...

Here's what we're thinking: We're considering building some automated testing to try to reliably reproduce the issue by just sending touch events in a certain way. This way we should...

Indeed, check point 6 of my OP: _6. When the issue happens, the onPressIn and onPressOut events are fired almost simultaneously with only a few milliseconds difference but onPress is...

> The issue is triggered when `useNativeDriver` is set to `true` as per this issue: #36504 > > `onPress` works until a translation animation -- with `useNativeDriver: true` -- occurs....