Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bottom navigation gets disappeared from the previous scene when the new one is pushed. #2894

Closed
igorarkhipenko opened this issue Feb 20, 2018 · 2 comments

Comments

@igorarkhipenko
Copy link

igorarkhipenko commented Feb 20, 2018

Version

  • react-native-router-flux v4.0.0-beta.27
  • react-native v0.53.0

Expected behaviour

Bottom navigation is expected to be on the previous scene when the animation of transition is producing.

Actual behaviour

Bottom navigation component disappears from the previous scene when the animation is producing.
bottomnavigation_bug

Steps to reproduce

  1. Create a bottom navigation with the button inside to transit to another container.
<Router createReducer={this._reducerCreate}>
  <Scene key="root">
    <Scene
      key="main"
      tabBarComponent={tabBarComponent}
      tabBarPosition="bottom"
      hideNavBar
      tabs
      initial={initial.dashboard}
    >
      {/* another scenes for tabBarComponent */}
      <Scene
        key="achievements"
        clone
        hideTabBar
        tabBarLabel="Achievements"
        component={Achievements}
        title="Achievements"
      />
      {/* another scenes for tabBarComponent */}
    </Scene>
    <Scene 
      key="personalRecords"
      component={PersonalRecords}
      title="Personal records"
    />
  </Scene>
</Router>
  1. Smoothly go back using gesture.
  2. Bottom navigation has disappeared from the previous scene.
@igorarkhipenko
Copy link
Author

I wonder if I'm doing something wrong or nobody else uses this kind of simple transition between scenes. If so, could you guys give me any advice about that please?

@aksonov
Copy link
Owner

aksonov commented Aug 8, 2018

Please try to reproduce it with Example project and latest version 4.0.0-beta.40. Feel free to open if the issue still exists

@aksonov aksonov closed this as completed Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants