Fab child buttons are "shown" initially/sometimes when active=false

react-native, react and native-base version

Other than my project, this also happens with current KitchenSink in Expo.

{
  "main": "node_modules/expo/AppEntry.js",
  "private": true,
  "scripts": {
    "test": "node ./node_modules/jest/bin/jest.js --watch"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "@expo/samples": "2.1.1",
    "@expo/vector-icons": "^6.2.1",
    "expo": "^23.0.0",
    "firebase": "^4.6.2",
    "moment": "^2.19.3",
    "native-base": "^2.3.3",
    "react": "16.0.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-23.0.0.tar.gz",
    "react-native-datepicker": "^1.6.0",
    "react-native-keyboard-spacer": "^0.4.1",
    "react-navigation": "^1.0.0-beta.19",
    "react-redux": "^5.0.6",
    "redux": "^3.7.2",
    "redux-logger": "^3.0.6",
    "redux-thunk": "^2.2.0",
    "validate.js": "^0.12.0"
  },
  "devDependencies": {
    "jest-expo": "^23.0.0"
  }
}

Expected behaviour

Fab child buttons are hidden when active=false.

Actual behaviour

Fab child buttons are “shown” initially, although partially covered or in different position. Let me show you what I mean.

KitchenSink, during first open: see that red button…?

My own app, during first open and “sometimes after toggling a few times”: see that very slight pink, that is a child button.

Note that there is no problem when active=true. The problem is only when active=false.

Is the bug present in both ios and android or in any one of them?

Only tested with Android 7.0 and Expo 23.

[pnoyens]

I still see this issue in Native Base 2.10.0 when FAB on position “bottomRight”. Should be reopened.

[Choem]

Hi all, still haven’t fixed the issue. I don’t have a workaround for the native base package. I used another FAB which was less cumbersome to work with together with the navigators I used for my project.