Tried to register two views with the same name #15

enzzoperez · 2019-08-15T18:57:21Z

Bug

I tried to add the picker, the compilation is fine, but when the app is open appears a red screen with the message:
Tried to register two views with the same name AndroidDropdownPicker

Update: I also use Native base in the project
Can you help me please?

Environment info

React Native Environment Info:
System:
OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 696.37 MB / 7.68 GB
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 8.9.0 - ~/.nvm/versions/node/v8.9.0/bin/node
Yarn: 1.15.2 - /usr/bin/yarn
npm: 5.5.1 - ~/.nvm/versions/node/v8.9.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 20, 22, 23, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.1, 25.0.2, 25.0.3, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.3, 28.0.3
System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.5429.30.34.5452501
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9
npmGlobalPackages:
react-native-cli: 2.0.1

React native info output:

 // Tried to register two views with the same name AndroidDropdownPicker

Library version: 0.59.9

Akhnaten972 · 2019-08-18T20:35:21Z

+1

danieljgp2 · 2019-09-05T20:29:51Z

Im facing this error too, this error seems to be related with the dependencies, there is probably a dependency working with the picker of react-native.

Any idea about how to fix it @jainkuniya ?

jainkuniya · 2019-09-05T20:37:17Z

Hi @danieljgp2, thanks for the report. Will look into it. It will be great if you could share some code snippet, through which it is easily reproducible

danieljgp2 · 2019-09-05T20:55:36Z

@jainkuniya which react native version are you using as a dependecy ? i dont know if the problem is related to any dependecy of my project or any dependency of the library but im pretty sure that problem is related with the changes of RN version after 0.59 and the deprecation of the Picker.

sofiageo · 2019-10-31T23:41:47Z

I ran into this issue. For me it was caused by a wrong import on my project, which was looking for react-native Picker. But what I noticed is that even on react-native 0.61.2 package, this PR was not included. It's probably not a bug just some libraries would need to update their imports.

Sroka · 2019-12-18T14:46:54Z

Any news on this? I have the same problem and cannot get rid of it :/ @sofiageo How did you manage to figure out where offending react-native Picker import was? I check my whole app and there are no usages of Picker. Tried to search in node_nodules to check if some lib uses it but no luck

sofiageo · 2019-12-18T16:14:23Z

Any news on this? I have the same problem and cannot get rid of it :/ @sofiageo How did you manage to figure out where offending react-native Picker import was? I check my whole app and there are no usages of Picker. Tried to search in node_nodules to check if some lib uses it but no luck

It was easy for me because I only had 2 imports of Picker. How are you searching in node_modules? If it is a multi-import from react-native you will have to only search for the word Picker.

The correct import should be import {Picker} from '@react-native-community/picker';

chakrihacker · 2020-01-03T12:41:15Z

Is this bug still exists??

danieljgp2 · 2020-01-03T14:02:34Z

@chakrihacker Probably it does, the bug is caused when a dependency imports the picker from react-native and you import the picker from react-native-community/picker

chakrihacker · 2020-01-03T18:44:33Z

@danieljgp2 The Android native view name is changed to RNCPicker from RCTPicker but previous versions have name RCTPicker. I think by updating dependency this issue will be solved.

johnjoshuadablo · 2020-04-22T08:31:56Z

+1

Library version: 0.59.9

orion151 · 2020-04-22T18:33:49Z

I have same issue.
"react-native": "0.62.2",
"@react-native-community/picker": "^1.3.0",

please solve this proble

chakrihacker · 2020-04-23T02:57:46Z

Is this happening in new rn versions?

orion151 · 2020-04-23T23:01:40Z

I found why this error occurs.

orion151 · 2020-04-24T07:41:41Z

Can you share your package.json file?

orion151 · 2020-04-24T07:49:09Z

In my case, I used @react-native-community/picker": "^1.3.0 and "react-native-google-places-autocomplete": "^1.4.1" in my project.
"react-native-google-places-autocomplete": "^1.4.1" used picker from react-native.
so, occured this error.
Perhaps, there are another pakage using picker from react-native like this in your project.

khalednailigit · 2020-04-24T14:21:02Z

+1

KawaljeetSBagga · 2020-04-27T11:35:14Z

+1. Did ANYONE get rid of this?

"react-native": "0.62.0",
"@react-native-community/picker": "^1.3.0"

hussainhspl · 2020-04-29T07:43:45Z

@danieljgp2 The Android native view name is changed to RNCPicker from RCTPicker but previous versions have name RCTPicker. I think by updating dependency this issue will be solved.

how to update dependency ?

hussainhspl · 2020-04-29T09:24:20Z

Is this happening in new rn versions?

yes i am using RN 0.62 app is not running and getting crashed,
and also using native base 2.13.12 version and rn picker ver 1.3.0

rpCal · 2020-04-30T07:22:17Z

On my code setup...

 <Picker
  selectedValue={formik.values.gender}
  accessibilityLabel={'gender'}
  onValueChange={(itemValue, itemIndex) => {
    formik.setFieldValue('gender', itemValue);
  }}>
  <Picker.Item label="Male" value="MALE" />
  <Picker.Item label="Female" value="FEMALE" />
</Picker>

Issue is related to field accessibilityLabel... If key is setup with any value = err!

jafar-jabr · 2020-05-05T14:26:24Z

if anyone still has this issue, make sure that you don't use "Picker" from an other package in my case it was "styled-components"

MrNoino · 2020-05-06T21:40:22Z

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

MrNoino · 2020-05-07T13:57:52Z

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

iYahya · 2020-05-07T13:59:23Z

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

MrNoino · 2020-05-07T14:20:42Z

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

mrinal-roy · 2020-05-22T10:20:01Z

@haocse the issue comes when we use { Picker } from @react-native-community/picker
With react-native this issue doesnot arise. But with react-native does the {Picker} work in iOS ?

haocse · 2020-05-25T08:45:21Z

@mrinal-roy-au2 Yes, iOS app works, this problem happens on the Android app

rassemdev · 2020-05-30T21:31:26Z

@haocse Picker in React-Native is deprecated. And they are suggesting this one. So need to sort this out within it.

sfarkas1988 · 2020-06-01T10:36:47Z

Same issue here. using import { Picker } from 'react-native' is not a solution as suggested by @haocse

rassemdev · 2020-06-02T20:25:14Z

anybody found any solution except importing from RN!

introin · 2020-06-07T19:07:42Z

+1

zouhairjabiri · 2020-06-10T01:03:14Z

I Fix this probleme by :
Removing import { Picker } from '@react-native-community/picker';
And use import { Picker } from 'react-native'

ovidiumunteanu · 2020-06-13T09:56:03Z

Same Here.
Is there any solution?
I think my error comes from Picker from @react-native-community/picker and react-native-country-picker-modal

adrian1388 · 2020-06-16T02:28:56Z

May be you all still are using Picker from 'react-native' somewhere in your project.
Be sure to not import from 'react-native'

Even I can use {Picker} from '@react-native-community/picker' inside styled-components this way:

const MyPicker = styled(Picker)...

This was my case.

LohanaPawan · 2020-06-16T15:15:53Z

In my case, I used @react-native-community/picker": "^1.3.0 and "react-native-google-places-autocomplete": "^1.4.1" in my project.
"react-native-google-places-autocomplete": "^1.4.1" used picker from react-native.
so, occured this error.
Perhaps, there are another pakage using picker from react-native like this in your project.

Makes sense, but could you please help to understand that how we can know exactly which dependency is in clash with the picker library and how to solve the issue.

introin · 2020-06-16T18:00:43Z

For now, I have started using Picker from native base library and the issue appears fixed for me albeit few design issue I needed to address in such.

saim1309 · 2020-06-18T02:43:06Z

I am also facing the same issue may be for temporary basis I will use it from the react-native or native base. I am using only one picker in one of my components and the moment I import it from '@react-native-community/picker' it throws that error.
Anyways, if anybody come across the solution, please please let us know.

raymochi · 2020-06-18T03:51:34Z

So, I ran into this issue and got it working by changing the name of AndroidDropdownPicker to RNCAndroidDropdownPicker, did the same for dialogpicker.

I opened up a PR for the changes, you can see them here: #99

kesha-antonov · 2020-09-25T19:46:50Z

In my case I had 2 versions in yarn.lock

Added

"resolutions": {
    "@react-native-community/picker": "^1.8.0"
  },

to package.json to fix this

diogoaltoe · 2020-10-09T23:16:08Z

In my case, here is the way I found to temporarily solve the problem. It is obviously not the best way, but it was the one I found at the time.

GeekyAnts/NativeBase#3114 (comment)

hengkx · 2020-10-13T11:40:09Z

"@react-native-community/picker": "^1.8.1", same issue.

grekosys · 2020-11-07T19:09:03Z

Yo tenía el mismo problema. Lo solucione desinstalando react-native-picker-select. Esté tiene conflicto con native-base.

altany · 2020-12-08T16:03:34Z

We are importing two pickers in one scene, made sure to only import from @react-native-community/picker and not "react-native" and tried the trick with adding accessibility labels but I still get this error.

Can someone help with this as we currently have a broken app because of this.

Update: for some reason 1.9.4 was installed in our app. Downgrading to 1.9.3 for all dependencies (which was tested and working before) fixed the issue

MehmetKaplan · 2021-01-03T09:43:25Z

In my case I had 2 versions in yarn.lock

Added
"resolutions": {
    "@react-native-community/picker": "^1.8.0"
  },
to package.json to fix this

A similar approach solved my case within Expo 40 and for datetimepicker, not picker:

	"resolutions": {
		"@react-native-community/datetimepicker": "3.0.4"
	 },

Wei102193 · 2021-01-07T06:33:52Z

In my case I am using "@react-native-picker/picker": "^1.9.2", and "native-base": "^2.13.14".
Somehow the latest version of "native-base" is using picker from "@react-native-community/picker" which has been deprecated. I believe this is what caused the problem on my side. So I downgrade "native-base" to version 2.13.14 where they still import picker from "react native", and It works fine. Seriously "native-base" caused too much problems, I am thinking remove it completely from my project. Hope this helps someone.

MehmetKaplan · 2021-01-07T11:35:05Z

Seriously "native-base" caused too much problems, I am thinking remove it completely from my project.

Even though I respect the developers of the native-base, I could not have agreed more to above comment. It is generating more problems than it solves, especially with pickers.

nandorojo · 2021-01-10T21:18:51Z

I got a similar error upgrading from Expo SDK 39 -> 40. I solved it by uninstalling @react-native-community/picker and instead installing @react-native-picker/picker.

gluons · 2021-01-14T04:45:59Z

Uninstall old @react-native-community/picker and install latest @react-native-picker/picker solve this problem for me.

jdoherty61 · 2021-01-16T18:42:04Z

#45 (comment) - Was stuck on this for a bit and came across this comment.

guicompeng · 2021-01-20T16:35:59Z

#15 (comment) and #15 (comment)
Thanks, it worked for me.

iguilhermeluis · 2021-01-21T13:54:10Z

 <Picker
  selectedValue={formik.values.gender}
  accessibilityLabel={'gender'}
  onValueChange={(itemValue, itemIndex) => {
    formik.setFieldValue('gender', itemValue);
  }}>
  <Picker.Item label="Male" value="MALE" />
  <Picker.Item label="Female" value="FEMALE" />
</Picker>

it work for me!

DimanshaMalrindu · 2021-01-25T03:21:24Z

The Author renamed the library to @react-native-picker/picker. See the GitHub new repository: https://github.com/react-native-picker/picker It will resolve the issue after uninstalling the @react-native-community-picker library and rename the imported pickers to @react-native-picker/picker. If you use some other features in the @react-native-community, just rename the imported react-native-community/picker to react-native-picker/picker

nayookyaw · 2021-03-03T10:01:24Z

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

vijaychouhan-rails · 2021-05-22T06:50:22Z

I installed the NativeBase version that installed "@react-native-picker/picker" "^1.9.7" as dependency and by mistake, I install @react-native-picker/picker too.
So to solve this issue: remove the @react-native-picker/picker that you installed because of NativeBase already installed @react-native-picker/picker as a dependency, if you are using yarn then check on yarn.lock file

dan-fein · 2021-11-30T02:57:25Z

I actually realized I didn't need native-base so I just deleted it (which I know isn't possible for everyone) and that worked. I did a little more research after and it looks like I could have upgraded native-base to the latest version and it would have worked. Hope that helps anybody struggling with this one!

jainkuniya self-assigned this Aug 20, 2019

chakrihacker closed this as completed Jan 3, 2020

appukuttan-shailesh mentioned this issue May 3, 2020

Tried to register two views with the same name AndroidDropdownPicker lawnstarter/react-native-picker-select#320

Closed

majugurci mentioned this issue May 8, 2020

Picker has been extracted from react-native core GeekyAnts/NativeBase#3114

Closed

Tried to register two views with the same name #15

Tried to register two views with the same name #15

Comments

enzzoperez commented Aug 15, 2019 • edited Loading

Bug

Environment info

Akhnaten972 commented Aug 18, 2019

danieljgp2 commented Sep 5, 2019

jainkuniya commented Sep 5, 2019

danieljgp2 commented Sep 5, 2019

sofiageo commented Oct 31, 2019 • edited Loading

Sroka commented Dec 18, 2019

sofiageo commented Dec 18, 2019 • edited Loading

chakrihacker commented Jan 3, 2020

danieljgp2 commented Jan 3, 2020

chakrihacker commented Jan 3, 2020

johnjoshuadablo commented Apr 22, 2020

orion151 commented Apr 22, 2020

chakrihacker commented Apr 23, 2020

orion151 commented Apr 23, 2020

orion151 commented Apr 24, 2020

orion151 commented Apr 24, 2020

khalednailigit commented Apr 24, 2020

KawaljeetSBagga commented Apr 27, 2020 • edited Loading

hussainhspl commented Apr 29, 2020

hussainhspl commented Apr 29, 2020

rpCal commented Apr 30, 2020

jafar-jabr commented May 5, 2020

MrNoino commented May 6, 2020

MrNoino commented May 7, 2020

iYahya commented May 7, 2020

MrNoino commented May 7, 2020

mrinal-roy commented May 22, 2020 • edited Loading

haocse commented May 25, 2020

rassemdev commented May 30, 2020

sfarkas1988 commented Jun 1, 2020

rassemdev commented Jun 2, 2020

introin commented Jun 7, 2020

zouhairjabiri commented Jun 10, 2020 • edited Loading

ovidiumunteanu commented Jun 13, 2020

adrian1388 commented Jun 16, 2020

LohanaPawan commented Jun 16, 2020

introin commented Jun 16, 2020

saim1309 commented Jun 18, 2020

raymochi commented Jun 18, 2020

kesha-antonov commented Sep 25, 2020

diogoaltoe commented Oct 9, 2020

hengkx commented Oct 13, 2020

grekosys commented Nov 7, 2020

altany commented Dec 8, 2020 • edited Loading

MehmetKaplan commented Jan 3, 2021

Wei102193 commented Jan 7, 2021 • edited Loading

MehmetKaplan commented Jan 7, 2021

nandorojo commented Jan 10, 2021

gluons commented Jan 14, 2021

jdoherty61 commented Jan 16, 2021 • edited Loading

guicompeng commented Jan 20, 2021 • edited Loading

iguilhermeluis commented Jan 21, 2021

DimanshaMalrindu commented Jan 25, 2021 • edited Loading

nayookyaw commented Mar 3, 2021

vijaychouhan-rails commented May 22, 2021

dan-fein commented Nov 30, 2021

enzzoperez commented Aug 15, 2019 •

edited

Loading

sofiageo commented Oct 31, 2019 •

edited

Loading

sofiageo commented Dec 18, 2019 •

edited

Loading

KawaljeetSBagga commented Apr 27, 2020 •

edited

Loading

mrinal-roy commented May 22, 2020 •

edited

Loading

zouhairjabiri commented Jun 10, 2020 •

edited

Loading

altany commented Dec 8, 2020 •

edited

Loading

Wei102193 commented Jan 7, 2021 •

edited

Loading

jdoherty61 commented Jan 16, 2021 •

edited

Loading

guicompeng commented Jan 20, 2021 •

edited

Loading

DimanshaMalrindu commented Jan 25, 2021 •

edited

Loading