onValueChange not called on android when there is only one option about picker

[bill2004158]

I have got the similar issue with any items.
the picker will auto select the first item by default.
thus when user choose the first item, onValueChange() will NOT be called.
any options to disable "select the first item by default"?

[wissemContractor]

onValueChange needs the value to be changed, so if there is just one item it will be selected automatically, so when selecting it the onValueChange will never be called,
i am facing a similar issue when i reselect the same item,
we need a new props like onValueSelected, that's would be general

[stevehanson]

We were able to somewhat work around this issue on my current project by inserting an option at the top of the list of options and using it as the picker prompt instead of using the androidPrompt prop on Picker. We style that option with a bigger font size to distinguish it as a header. This option has a bogus value, and we ignore this value in onValueChange if the option was selected.

<Picker
  selectedValue={selectedValue}
  onValueChange={(value) => {
    if (value !== EMPTY_LABEL_VALUE) {
      onChange(value);
    }
  }}
>
  <Picker.Item
    label={androidPrompt}
    value={EMPTY_LABEL_VALUE}
    style={styles.pickerAndroidPrompt}
  />
  {options.map((option) => (
    <Picker.Item
      key={option.value}
      label={option.label}
      value={option.value}
      style={styles.pickerAndroidItem}
    />
  ))}
</Picker>

Minor notes:

• Styling the first option with font weight did not work
• When we set the font size for the first option, there were some weird issues where other options randomly had the larger font. To work around that, we had to explicitly set the font size in the other options

[orzhtml]

+1

[CyxouD]

Same for iOS. However, it is possible to scroll up, then down and select an option because of the scroll bouncing

[DnEgorWeb]

Hey, guys, have you found any workaround for this? I'm also facing a situation when onValueChange is not called for the first item

[DnEgorWeb]

Hi @Naturalclar, do you know is there a way to avoid this bug besides explicitly setting the first item as a default value? If I get it right from the source code the problem comes from native android picker

[villanuevadani]

Having the same issue as @DnEgorWeb . Did you guys find a solution for this?

If not, I would proceed with adding the first item with a placeholder label that has as value the 'undefined' string. That appears to be working:

<Picker.Item label={'--None--'} value={'undefined'}/>

[ayozebarrera]

On my case, I have forms with Pickers not required, so the user could leave them empty... So if they choose an item, they could need to clear the picker after that so I'm adding this before items

<Picker.Item label={''} value={''} />

and works perfectly for me

[Roytangrb]

I believe this could be fix on Android, but need quite some effort

Had a quick look at the implementation:

picker/android/src/main/java/com/reactnativecommunity/picker/ReactPicker.java

Line 37 in fe71dbb

public void onNothingSelected(AdapterView<?> parent) {

At this line here, the native event with position value -1 should be emitted for our JS control component to handle, in case of no value selected or picker has no option items?

But neither setting selectedValue={undefined} nor giving to Picker.Item will trigger onNothingSelected callback.

If the owner may provide some guidance, I am down for helping with this.

Another related point to note is that for AdapterView.onItemSelected

This callback is invoked only when the newly selected position is different from the previously selected position or if there was no selected item.

Is it possible to use AdapterView.OnItemClickListener instead to have more picker control ?
@Naturalclar

[v-kryuchkov]

Same issue. Did you guys find a solution for this?

[marlti7]

Same issue. Did you guys find a solution for this?

[csamet07]

Same issue. Did you guys find a solution for this?

[Livijn]

This is still a big issue. onValueChange isn't fired even when specifying selectedValue to other than the first option's value. How is this not fixed?

My temporary fix is to add <Picker.Item enabled={false} /> as a first item but that looks awful.