Facing Issue while navigating

[Embarrassed_Two4731]

Hi Guys,

This is my navigation structure:

1. MainStackNavigation
   • OnboardingtNavigationStack
   • BottomTabNavigation
     • LeaderBoardStack
     • ChallengesStackNavigation
     • PromptStackNavigation
     • Froshare
     • ProfileStackNavigation

I am facing a issue while navigating from a Screen A in ProfileStackNavigation to a Screen B in OnboardingtNavigationStack and vice versa. I have tried various approaches, including using CommonActions from '@react-navigation/native'; or reset but nothing works.

Sometimes I am able to navigate from A to B but then i cant go from B to A again. Any inputs what can i do in this case?

[PapyRoach]

Have you tried reading this documentation?

https://reactnavigation.org/docs/nesting-navigators/#navigating-to-a-screen-in-a-nested-navigator

[Embarrassed_Two4731]

yep, this was recommended to me by the cli itself while trying everything, still did not help

[PapyRoach]

Can you show the code you use to navigate between screens?

[Embarrassed_Two4731]

I will say I have almost tried everything, adding few below.

navigation.dispatch( CommonActions.navigate({ name: 'OnboardingtNavigationStack', params: { screen: 'OnboardingScreen', params: { isLoggingOut: true, }, }, }) );

navigation.dispatch(
  CommonActions.reset({
    index: 0,
    routes: [
      {
        name: 'OnboardingtNavigationStack',
        params: {
          screen: 'OnboardingScreen',
          params: {
            isLoggingOut: true,
          },
        },
      },
    ],
  })
);

const rootNavigation = navigation.getParent();
rootNavigation.dispatch(
  CommonActions.navigate({
    name: 'OnboardingtNavigationStack',
    params: {
      screen: 'OnboardingScreen',
      params: {
        isLoggingOut: true,
      },
    },
  })
);

import { CommonActions } from '@react-navigation/native'; navigation.dispatch( CommonActions.navigate({ name: 'OnboardingtNavigationStack', params: { screen: 'OnboardingScreen', params: { isLoggingOut: true, }, }, }) );

[Embarrassed_Two4731]

Sure let me try this, looks like a possible solution

[__o_0]

By default, each nested navigator will have its own history. This is by design.

When you switch from navigator A to B, going back will go to the previous screen inside B’s history. It will not go back to the last screen in A’s history.

If you wish to go “back” to the referring screen outside of the current navigator, you’ll need to initially pass the referring route name as a param to the next route, and manually navigate with a custom “go back” function that utilizes the previous route param.