-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MotiPressable stops firing onPresses on Android #179
Comments
Did you wrap your app in the gesture handler root view? |
Yeah |
hm, under the hood we’re using TouchableWithoutFeedback from RNGH. Can you see if that works? I wonder if it’s because TouchableWithoutFeedback is wrapped with createAnimatedComponent in MotiPressable? |
I tried using pure |
@agallio Were you able to fix it by passing the style props? |
I see that this fix is suggested: containerStyle={{ flex: 1 }}
style={{ flex: 1 }} Maybe you could try wrapping the element with a |
Unfortunately not, @grgmgd. Tried using both style prop. And even tried wrapping the component with |
I wonder if we should use |
I was able to fix it by wrapping my app with the new |
It seems like some people are still facing this issue. |
Published a fix at
|
Same problem on the device, in the emulator it works fine, but it doesn't work on the real device. This is interesting because I use it in two components, and in one component it works, but not in the second, both inside the BottomSheet:
This one works inside flatlist:
|
are you on the latest moti |
@nandorojo "moti": "^0.25.1" |
I'm using it as a button that has an absolute position above the map. |
removed AP from FAB because of nandorojo/moti/issues/179
Same issue as @devoren ... I am on Moti 0.26.0. Is there still no known fix for this? My button is also absolutely positioned. Sometimes the onPress fires and sometimes it does not (Only on android) |
On Android (emulator and device),
MotiPressable
stops firing theonPress
after a couple of times or doesn't fire it at all, whilePressable
works fine. 🤔 iOS has no issues.Any idea why this might be and/or what the fix is?
I've tried it on the latest RNGH and it happens still.
The text was updated successfully, but these errors were encountered: