4.2.2 broke android default value
See original GitHub issueEnvironment
Android react-native-slider 4.2.2
Description
Upgrading from 4.2.1 to 4.2.2 broke the slider’s default value. Using value={3}
(for example), minimumValue={1}
, and maximumValue={5}
will render the slider with a default value of 3 on 4.2.1, but 1 on 4.2.2
Reproducible Demo
Issue Analytics
- State:
- Created a year ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
CheckBoxPreference default value not working [36914268]
I had that problem on Android 4.2.2. ... Checkbox preference does not initially exist at all if the default value is set to...
Read more >Known issues with Android Studio and Android Gradle Plugin
To fix the issue for the current project, click Run > Edit Configurations and change the default JUnit configuration to only include the...
Read more >my status bar in android 4.2.2 emulator is broken
Today I found the status bar in android 4.2.2 emulator is broken.I cannot pull it down. I have no idea what happened. android...
Read more >Android App build error - I have no idea what to do
:@react-native-firebase_app:firebase.bom using default value: 28.1.0 ... minimum supported version (30.0.2) for Android Gradle Plugin 4.2.2.
Read more >Secure USB debugging in Android 4.2.2
Official release notes for Android 4.2.2 don't seem to be available ... The ADB host authentication functionality is enabled by default when ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looks like
onValueChange
is called right after the component mounts (Android only) with theonValueChange
instead of w/e was set tovalue
.This happens for me as well on 4.2.0
What is strange is on certain build devices it works and others it does not. If I build the same code on one computer vs another I get a different result. Sometimes it works properly and sometimes it behaves as the OP said.