MotiPressable stops firing onPresses on Android
See original GitHub issueOn Android (emulator and device), MotiPressable
stops firing the onPress
after a couple of times or doesn’t fire it at all, while Pressable
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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Pressable not working in react-native android - Stack Overflow
When a child of a pressable component is pressed (such as an image), the function passed to the onPress prop does not execute...
Read more >TouchableWithoutFeedback not working with flexbox #864
I am having some trouble showing {children} when using this setup. If I use react-native's TouchableWithoutFeedback it works.
Read more ><MotiPressable /> | Moti
A near-replacement for React Native's Pressable component, with animations run on the native thread.
Read more >difference between pressable and touchableopacity - splunktool
Can someone more experienced explain how the Pressable differs from the TouchableOpacity and when it is better to use them. Fingers are not...
Read more >The React Native (+ Web) animation library, powered by ...
Sequence not working since reanimated 2.3.0. Since reanimated 2.3.0 I was no longer able ... Fix MotiPressable on Android, closing #179 #143 ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Published a fix at
0.0.18-alpha.15
.yarn add moti@canary
. Will be part of the v18 release.I tried using pure
TouchableWithoutFeedback
from RNGH and the result is the same. It won’t do anything when pressed. A related issue here: https://github.com/software-mansion/react-native-gesture-handler/issues/864. This also impacts solito’s MotiLink since it is using the same component under the hood.