-
Notifications
You must be signed in to change notification settings - Fork 499
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
Tried to register two views with the same name AndroidDropdownPicker #320
Comments
Also, the solution mentioned here did not work for me. All my imports of that component already were: |
sounds like the issue is using both this library and the newly abstracted Picker library. either that library will need to be updated to handle this scenario - or this'll be solved once #303 is merged in. |
i have the same issue |
Can confirm #303 solves this. For now you can use patch-package to switch this package to the community library. |
Any idea when this will be merged? |
I know this has been closed. 8.0.1 Fixed my iOS issues but it started breaking my Android build. |
@plgrazon worth opening a new report |
Build is failing for android |
I fixed this problema installing the following versions: |
|
I changed react-native-community/datetimepicker version from 2.4.0 to 3.0.9 "@react-native-community/datetimepicker": "^3.0.9" We can assume the old version will get error |
Describe the bug
Getting error with following message:
The error seems to be similar to this:
react-native-picker/picker#15
To Reproduce
Steps to reproduce the behavior:
In my project, I have used also this component:
import { Picker } from '@react-native-community/picker';
I believe it is a clash between these components. Any way to avoid this error and be able to use both?
Expected behavior
Be able to use this component without clashing with other components.
Screenshots
"n/a".
Additional details
Reproduction and/or code sample
The text was updated successfully, but these errors were encountered: