Cannot find element for parent=SCENE_NAME within current state

[jeroenbourgois]

Hi

I have the following Router setup

      <Router>
        <Scene key="modal">
          <Scene key="preloader" hideNavBar={true}  component={Preloader} initial={true}  title="Preloader" />
          <Scene key="login" component={Login} />

          <Scene key="sidemenu" component={SideMenu}>
            <Scene key="welcome" component={Welcome} title="Welcome" />
            <Scene key="home" component={Home} title="Home" />
          </Scene>
        </Scene>
      </Router>

When calling Actions.welcome() on another page, I get something like:

Cannot find element for parent=sidemenu within current state

I think I am doing something wrong with the nesting (SideMenu is a Drawer component) but cannot figure out what I am missing.

Thank you for this wonderful component!

[aksonov]

SideMenu should have single child, Scene container. Please try to reproduce the issue on component Example. Also you could try to debug by printing state within Reducer - reducer cannot find parent of 'welcome' action for some reason.

[jeroenbourgois]

Hi, I updated my code so that the SideMenu has a single child and I added the reducer. Still the same error, this is the output:

REDUCER -> ACTION: Object {type: "RootContainerInitialAction"}
REDUCER -> ACTION: Object {key: "home", type: "push"}
ACTION_CLICK -> Failed AssertionError {name: "AssertionError", actual: undefined, expected: true, operator: "==", message: "Cannot find element for parent=main within current…pe":"push","key":"0_preloader"}],"key":"0_modal"}"…}

This is my current router:

<Router createReducer={reducerCreate}>
        <Scene key="modal" hideNavBar={true}>
          <Scene key="login" type="replace" component={Login} title="Inloggen" />
          <Scene key="welcome"  hideNavBar={true} component={Welcome} title="Welcome" />
          <Scene key="preloader" hideNavBar={true} component={Preloader} initial={true}  title="Preloader" />

          <Scene key="sidemenu" component={SideMenu}  title="ballekes">
            <Scene key="main" navBar={NavBar}>
              <Scene key="home" component={Home} title="Home" />
            </Scene>
          </Scene>
        </Scene>
      </Router>

For now I can bypass the issue by letting the action call sidemenu but then the animation let's the sidemenu slide out real fast :) bit weird.

Thanks for your efforts

[aksonov]

Could you modify Example project to reproduce the issue?

[jeroenbourgois]

Ok, I will do it asap. Meanwhile I dropped two minor PR's ;) I am not super technical so it are two documentation updates, but hey, my way of helping out, appreciate your feedback on my issues so I need to give something back :)

[aksonov]

You may also print incoming state passed to defaultReducer to understand why it cannot find parent...

[jeroenbourgois]

Ok, I can reproduce with the Example project. Modification is very easy:

Change line 14 that says

<Button onPress={Actions.register}>Go to Register page</Button>

To (the change is the actions, where I want to trigger a nested view like 'loginModal', which is similar what I was doing:

<Button onPress={Actions.loginModal}>Go to Register page</Button>

Then the same error is thrown.

[spaceoi]

Got the same error.

[slamus]

I've got the same error.
I've got around it by setting initial={true} to my equivalent of your 'welcome' route.
Then I just need to call the parent route to go to this this route.

      <Router createReducer={reducerCreate}>
        <Scene key="root" hideNavBar={true} component={MainContainer}>

          <Scene
            key="Login"
            type="replace"
            component={LoginPageContainer}
            initial={true}
          />
          <Scene
            key="ProfileCompleteness"
            type="replace"
            component={ProfileCompletenessPageContainer}
          />

          <Scene
            key="Platform"
            type="replace"
            component={PlatformContainer}
          >
            <Scene
              key="Lobby"
              type="replace"
              initial={true}
              component={LobbyPageContainer}
            />
            <Scene
              key="PageTest"
              type="replace"
              component={PageTestContainer}
            />
            <Scene
              key="Profile"
              type="replace"
              component={ProfilePageContainer}
            />
            <Scene
              key="EditProfile"
              type="replace"
              component={EditProfilePageContainer}
            />
            <Scene
              key="Friends"
              type="replace"
              component={FriendsPageContainer}
            />
            <Scene
              key="AboutUs"
              type="replace"
              component={AboutUsPageContainer}
            />
            <Scene
              key="Show"
              type="replace"
              component={ShowPage}
            />
          </Scene>


        </Scene>
      </Router>

[aksonov]

So you want to go inside tabs container (i.e jump + push) ? Is it duplicate of #350 ?

[jeroenbourgois]

Not not that I know. I just want to navigate directly to a route inside my sidemenu (drawer). It also has a key but I cannot access keys inside. This does not really seem like push jump? When using the example I get the same error

[gustavovnicius]

@aksonov I've found something that I dont know if it is correct:

My Scenes are configured like this:

And...

This is a log from Reducers.js:17, note that only the "login" scene is on children, and at Reducers.js:20 it iterates on children. The "drawer" scene shouldn't be listed there too? Looking at the code, I'm wondering if this could solve the problem because at Reducers.js:20 it iterates on state.children, if the children tree was complete, it would have found the correct scene (I am calling "Actions.content()" inside the "login" scene). Am I wrong?

[aksonov]

@gustavovnicius Good catch! Looks like you are right, Reducer should iterate also over 'scenes' where all scenes are stored.

[aksonov]

@gustavovnicius However Drawer should have only one child, check example.