I'm having the same problem with animations when I reset or navigate backwards more than 1 screen. Here's the StackOverflow question

I have the same issue also. I am wondering if using a custom Transitioner would allow resetting the stack without any animations: https://reactnavigation.org/docs/views/transitioner

@diegorodriguesvieira hey, you need not to jump to another page, just use header null , and setstate in one page render different component

@diegorodriguesvieira i don't understand?

@aqnaruto but if I just navigate to a page without a header, I'll still have the navigation stack with the items because it has not been reset, can I have performance issues with that?

@LaurensLang I need to reset to the first navigation page inside the tab, however without seeing the animations for each card in the stack

@davidysong I will try, thanks

+1 anyone with a solution?

+1

+1

+1

@diegorodriguesvieira did you figure this out yet? What you are trying to accomplish is basically default iOS behaviour and should work out of the box ideally.

Here's a concise proposal that will fix this in many other issues:

#1663

This solution worked for me. Note that if you have 4 screen A, B, C, D and want to back from D to A, you have to call NavigationActions.back with key of B

backToRoute = (navigation, name) => {
    const routes = navigation.state.routes
    for (var i = 0; i < routes.length - 1; i++) {
      if (routes[i].routeName == name) {
        navigation.dispatch(NavigationActions.back({ key: routes[i + 1].key }))
        break
      }
    }
  }
```

closing since this was fixed by #2520, but feel free to reopen in case the issue persists

@vonovak #2520 does not work as intended.

After almost giving up on react-navigation I found your example for extending the NavigatorService but it is incomplete, it's missing the return for when there are no nested navigators.

function getRouteWithName(navigationState, name) {
  if (!navigationState) {
    return null;
  }
  const route = navigationState.routes[navigationState.index];

  // dive into nested navigators
  if (route.routes) {
    // NOTE +1 is because goBack accepts from, not to!
    const index = route.routes.findIndex(r => r.routeName === name);
    if (index > -1) {
      return route.routes[index + 1];
    }
    return getRouteWithName(route, name);
  } else {
    const index = navigationState.routes.findIndex(r => r.routeName === name);
    if (index > -1) return navigationState.routes[index + 1];
  }

  return null;
}

does this issues solved? In iOS we can simply push viewcontrollers by nav just disable the animation.

• 1 ..

welcome to RNRF, easy case for that~

How is it solved in RNRF @dustturtle

@luqmanrom it is not solved there as well. RNRF is based on React Navigation.
see aksonov/react-native-router-flux#2713

can someone please create a new issue for this and include a link to an example reproducing it on https://snack.expo.io or github? please without any superfluous code. I'd be happy to investigate. thanks!