-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Related pickers crashes the app #25998
Comments
Please use https://github.com/react-native-community/react-native-picker, and report issues there. Thank you |
Sorry, I thought it was a builtin feature. Thanks! |
It was but moved out |
@clamiax Looks like its a bug with version 0.60.4.
|
@vyshakh I already solved this way: react-native-picker/picker#14 (comment) Thanks! |
It seems impossible to bind two pickers together (one changing depending on the value of the other) because in 99% of cases the app crashes. It's a bug somewhere in the RN code which I was not able to workaround. The snippet below should make everything clears.
For now, I was forced to replace the pickers with custom modals.
React Native version:
System:
OS: Linux 4.18 Ubuntu 18.10 (Cosmic Cuttlefish)
CPU: (4) x64 Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
Memory: 1.91 GB / 3.73 GB
Shell: Unknown - /bin/mksh
Binaries:
Node: 8.11.4 - /usr/bin/node
npm: 6.10.3 - /usr/local/bin/npm
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.4 => 0.60.4
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-screens: 1.0.0-alpha.23
Steps To Reproduce
Bar > BarSub02
then go back toFoo
I expect to find
Foo > FooSub01
selected. I get a FATAL EXCEPTION instead.Following code example is a reproducible test case:
Notice that the issue does not occur if current item is the first in list or if you switch between groups with more than one item (e.g. if you add
FooSub02
underFoo
the issue should not happen anymore).Here's an excerpt from my logs:
The text was updated successfully, but these errors were encountered: