Open vibhor-d11 opened 8 months ago
Hi @IsaiaPhiliph When will there be a new version release for https://github.com/IsaiaPhiliph/react-native-snap-carousel-v4? We wanted to make use of the changes merged mentioned in this issue. Reference Github PR - https://github.com/IsaiaPhiliph/react-native-snap-carousel-v4/pull/1
Is this a bug report, a feature request, or a question?
Bug Report
Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an
x
character between the square brackets ([]
).)Have you made sure that it wasn't a React Native bug?
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
It is specific to android, however it is not easily reproducible but we have instances of this crash on our firebase for our users.
Is the bug reproductible in a production environment (not a debug one)?
Not reproducible but occuring for large userbase.
Environment
Android (12.0)
Expected Behavior
Should run fine with given default configurations
Actual Behavior
Currently their is no provision to enable/disable useNativeDriver for react native snap carousal. For carousal animations
useNativeDriver
is set to true i.e they run on UI thread by default. We encountered some crashes related to Animated node that occurred only on Android 12 devices and after digging into it we get to know it is related to useNativeDriver set to true for carousal animations. Also their is an open issue in react-native related to this crash: Link. So we added a patch inreact-native-snap-carousal
library for disabling useNativeDriver for devices having Android 12 and that reduces the crash rate for that crash with very few instances now. We have been using this for almost a year and haven't faced any issue with our app exposed to more than 20 million users. So we though of adding support for enable/disable useNativeDriver for react-native-snap-carousal as a exposed prop.Reproducible Demo
Not reproducible but occuring for large userbase having instances on firebase.
Steps to Reproduce
Their is no defined steps to reproduce this issue but we instances of this crash in our firebase for large numbers of users and it was reduced by setting useNativeDriver to false. Here is the stacktrace for it.