iOS implementation does not respect value prop

Simplified version: On iOS, the checkbox ALWAYS changes state when clicked/tapped, even when an explicit value is set. This is only the case in iOS; on Android, the checkbox respects the value prop even when it does not change after a click/tap.

To reproduce (iOS): <CheckBox disabled={ false } value={ true } onValueChange={(newValue) => console.log(newValue)} />

Now, try clicking/tapping the box. It will still become unchecked and “onValueChange” will still run" despite the value being explicitly set to true.

[LogicAnalysis]

Any work around for this? This problem makes it basically not usable if one have any custom logic for the checkbox.

I ended up making a custom wrapper around this component with a state that basically sets a timer for 0ms after the click, and if the provided value hasn’t changed, it changes the state back to the value. If you’re interested, let me know and I can post the code for it when I have time later.

Seems a really cool work around, thanks for the help.

You’re welcome! Let me know if you have any issues implementing it, and I can post my code as I’d have to modify it a bit to take out some static values specific to my organization.

[pieterprovoost]

Can confirm that on Android the checkbox becomes unchecked as well, despite value being set to true.