-
Notifications
You must be signed in to change notification settings - Fork 501
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
Crashing App on Android - React Navigation v5 & useNativeDriver #442
Comments
Same here |
I saw a similar issue with another picker library, (Android crashing upon touch event on picker component) here. Checkout Rapomon's workaround. Seems to work for this library too. The gist is to put an absolutely positioned empty Text element on top of the picker component. Here's how my code looks : <View style={{ flex : 1 }}>
<RNPickerSelect
items={myItems}
value={myValue}
placeholder={myPlaceholder}
onValueChange={myChangeHandler}
/>
<Text
style={{
width: '100%',
height: '100%',
position: 'absolute',
bottom: 0,
left: 0,
}}>
{' '}
</Text>
</View> |
you could use this solution here |
@ejilee thanks |
Thanks, working for me too |
First of all, I may not be able to express myself properly because my English is not good but i will try.
Describe the bug
I am using react-navigation v5. As you know, it keeps screen status for we can go to same page second times.
I use { useNativeDriver: true }
in Animated.event()
in onScroll event in Animated.ScrollView component in a stack screen.
This is only an example. There is same problem any pages what it is using useNativeDriver:true.
If i visit this screen and after then press any RNPickerSelect, my app is crashing.
But if i don't visit this screen, RNPickerSelect is works normally.
It is enough to visit this page only once.
To Reproduce
If i change status of useNativeDriver value to false, RNPickerSelect works fine. But this time, my animations work badly. I can't do this on my project.
Expected behavior
n/a
Screenshots
n/a
Additional details
Reproduction and/or code sample
n/a
The text was updated successfully, but these errors were encountered: