[Checkbox] [Android] "transparent" tick / alpha values not working in React Native 0.57.2
See original GitHub issueI have gone through these following points
- Check latest documentation: https://docs.nativebase.io/
- Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
- Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
- Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-
Issue Description
Libs version:
Node: 8.11.2 npm: 6.4.1 react-native: 0.57.2 react: 16.5.2 native-base: 2.8.1 I’m not using expo.
node, npm, react-native, react and native-base version, expo version if used
Expected behaviour
Checkbox tick is transparent when unchecked.
Actual behaviour
Checkbox tick is visible. Changing NativeBase exported variables don’t fix it.
Steps to reproduce
Add CheckBox native-base component:
<CheckBox onPress={() => { return; } checked={this.state.isChecked} />
Is the bug present in both iOS and Android or in any one of them?
Android only.
Any other additional info which would help us debug the issue quicker.
Proposed fix:
Include ‘textShadowRadius: 0’ in ‘react-native-vector-icons’ style property
File: Checkbox.js line 41
<IconNB style={{ ... textShadowRadius: 0 }} />
There is an open discussion about the issue in ‘react-native-vector-icons’: https://github.com/oblador/react-native-vector-icons/issues/863 This is the proposed fix for the time being. Thanks for your time.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top GitHub Comments
Hey Folks,
Now I checked that this fix is not already released, temporally I changed my package.json to import
"native-base": "git+https://github.com/GeekyAnts/NativeBase.git#e96c997492d898d812243d7f19297189c75af4c0",
But would be awesome to have this amazing fix released, so what do you think @SupriyaKalghatgi ? Would be great having a v2.8.2 patch with this fix.
Hey, Folks @rreina @SupriyaKalghatgi I think we are facing the same problem on 0.57.5, have you noticed this?