react-native: 0.46.4
react: 16.0.0-alpha.12
native-base: 2.3.1
Only affects Android
Expected Behavour:
Background color of main FAB button should match color in style prop.
Actual Behavour:
Background color of main FAB button is blue
<Fab
active={this.state.splitFabActive}
position="bottomRight"
style={{backgroundColor: '#000000'}}
onPress={() => this.setState({ splitFabActive: !this.state.splitFabActive })}
>
<Icon name={(this.state.splitFabActive?"close":"albums")} />
<Button style={{ backgroundColor: colors.headerBackground }} onPress={() => this._addSplit() }>
<Icon name="add" />
</Button>
<Button style={{ backgroundColor: '#666' }} onPress={() => this._removeSplit() }>
<Icon name="trash" />
</Button>
</Fab>
is this issue fixed? i am facing the same issue in android
Same here, blue background color...is this issue fixed ?
Same thing here too. Do you have any idea when this will be fixed ?
Same issue here. On iOS works properly. On Android the color don't change.
Same problem, what about fix? @shivrajkumar
He fixed it but didn't release yet
For now I required it directly from master like this "native-base": "GeekyAnts/NativeBase",, working fine
Hello - we hit the same bug. Do you have a plan to issue a release that will contain that fix ?
Is this going to be fixed?
Facing same problem here. Can't change the color of Fab.
For me, I installed directly from Git which may not be ideal, but it includes the fix untill they issue another release:
npm install --save native-base@https://github.com/GeekyAnts/NativeBase
It does not work npm install --save native-base@https://github.com/GeekyAnts/NativeBase because components folder does not exist anymore. Guess I will have to drop Fab for now.
Same problem here, do you have any plans to solve?
I hit the same problem also.
It would be really appreciated if any fixes can release for us. =)
@crossRT @FelipeBohnertPaetzold @TitanKing @dominic3 @vgabdala @MHaendel @philjoseph This has been fixed and released. Check v2.3.2
Most helpful comment
@crossRT @FelipeBohnertPaetzold @TitanKing @dominic3 @vgabdala @MHaendel @philjoseph This has been fixed and released. Check v2.3.2