-
Notifications
You must be signed in to change notification settings - Fork 272
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
bug: don't work: no label and no value #536
Comments
I have same issue. |
Same issue |
I have the same issue. ver 2.5.1 seems to work for me |
I added the prop style={{ fontSize: 14 }}, and it works for me: |
This works for me! Thank you! |
Setting font size also worked for me - glad I checked out the issues tab! Thank you 🙌🏻 |
fontSize working but I cant do it on all my pickers. |
the fontSize has made no difference to mine. Edit: I am using expo and once I created a new development build it worked just fine. Must have been a mismatch of native and javascript versions I guess. |
Updating @react-native-picker/picker from 2.4.0 to 2.6.1 - [updated package references]() - [chore run `yarn`]() - [updated demo package references]() - [chore run `yarn` in demo]() - [Resolved Android render issues]() On Android, starting after v2.5.1, an issue occurs where a zero font size is used for the picker. See notes: react-native-picker/picker#536 Upgrading Expo seems to resolve the issue. However, we decided that it would be better to include a fix in our wrapper. - A default fontSize has been added to `<Picker.item>` - iOS is not affected by this issue and has not been changed Illustration of bug: https://github.com/Instawork/hyperview/assets/127122858/71029ef9-c335-4ef1-bdcb-ef3272dac9b5 | v2.4.0 | v2.6.2 (w/ 16 default) | | -- | -- | | ![v-2-4-0](https://github.com/Instawork/hyperview/assets/127122858/590b0836-66d1-4af8-a0f2-34bf41dd5d39) | ![v-2-6-0-size16](https://github.com/Instawork/hyperview/assets/127122858/19c5d52a-d425-413f-8a3c-148eba1dbc8d) | Asana: https://app.asana.com/0/0/1206718044236459/f
The text was updated successfully, but these errors were encountered: