undefined is not an object (evaluating 'routes[state.index].key')





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am working on an app using react-native and react-navigation and when executinng the code:



            const reset = StackActions.reset({
actions: [
NavigationActions.navigate({
index: 0,
routeName: "intervention",
params: {
button: true
}
})
],
});
this.props.navigation.dispatch(reset);


below I have the following error: undefined is not an object (evaluating 'routes[state.index].key')



my first instinct was to do a grep but this was the result:



[jjulien@localhost appRoot]$ grep -r "routes[state.index].key"
[jjulien@localhost appRoot]$


I really have no idea where does it come from I search here on Stack OverFlow and on the GitHub of stack Navigation but no luck. Does somebody have an int where to search for or anything really?










share|improve this question





























    0















    I am working on an app using react-native and react-navigation and when executinng the code:



                const reset = StackActions.reset({
    actions: [
    NavigationActions.navigate({
    index: 0,
    routeName: "intervention",
    params: {
    button: true
    }
    })
    ],
    });
    this.props.navigation.dispatch(reset);


    below I have the following error: undefined is not an object (evaluating 'routes[state.index].key')



    my first instinct was to do a grep but this was the result:



    [jjulien@localhost appRoot]$ grep -r "routes[state.index].key"
    [jjulien@localhost appRoot]$


    I really have no idea where does it come from I search here on Stack OverFlow and on the GitHub of stack Navigation but no luck. Does somebody have an int where to search for or anything really?










    share|improve this question

























      0












      0








      0








      I am working on an app using react-native and react-navigation and when executinng the code:



                  const reset = StackActions.reset({
      actions: [
      NavigationActions.navigate({
      index: 0,
      routeName: "intervention",
      params: {
      button: true
      }
      })
      ],
      });
      this.props.navigation.dispatch(reset);


      below I have the following error: undefined is not an object (evaluating 'routes[state.index].key')



      my first instinct was to do a grep but this was the result:



      [jjulien@localhost appRoot]$ grep -r "routes[state.index].key"
      [jjulien@localhost appRoot]$


      I really have no idea where does it come from I search here on Stack OverFlow and on the GitHub of stack Navigation but no luck. Does somebody have an int where to search for or anything really?










      share|improve this question














      I am working on an app using react-native and react-navigation and when executinng the code:



                  const reset = StackActions.reset({
      actions: [
      NavigationActions.navigate({
      index: 0,
      routeName: "intervention",
      params: {
      button: true
      }
      })
      ],
      });
      this.props.navigation.dispatch(reset);


      below I have the following error: undefined is not an object (evaluating 'routes[state.index].key')



      my first instinct was to do a grep but this was the result:



      [jjulien@localhost appRoot]$ grep -r "routes[state.index].key"
      [jjulien@localhost appRoot]$


      I really have no idea where does it come from I search here on Stack OverFlow and on the GitHub of stack Navigation but no luck. Does somebody have an int where to search for or anything really?







      react-native react-navigation






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 16 '18 at 15:08









      julienjulien

      33




      33
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I haven't touched React Native or react-navigation but I'll take a shot!



          It looks like you have index set in the wrong spot.



          Taking a peek at the StackActions and NavigationActions docs, it looks like index belongs in the object you pass to reset rather than navigate. Try switching your code to be like this:





          const reset = StackActions.reset({
          index: 0,
          actions: [
          NavigationActions.navigate({
          routeName: "intervention",
          params: {
          button: true
          }
          })
          ],
          });


          Just as an added funfact, the code you were looking for isn't in your own codebase, rather it comes from the StackRouter.js file from react-navigation. When you run that StackActions.reset action, StackRouter later looks for the new value of index in its internal state. Because index wasn't defined in your code the router can't find the entry in its history that it should be referring to.



          Hope that does it! :D






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53340457%2fundefined-is-not-an-object-evaluating-routesstate-index-key%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I haven't touched React Native or react-navigation but I'll take a shot!



            It looks like you have index set in the wrong spot.



            Taking a peek at the StackActions and NavigationActions docs, it looks like index belongs in the object you pass to reset rather than navigate. Try switching your code to be like this:





            const reset = StackActions.reset({
            index: 0,
            actions: [
            NavigationActions.navigate({
            routeName: "intervention",
            params: {
            button: true
            }
            })
            ],
            });


            Just as an added funfact, the code you were looking for isn't in your own codebase, rather it comes from the StackRouter.js file from react-navigation. When you run that StackActions.reset action, StackRouter later looks for the new value of index in its internal state. Because index wasn't defined in your code the router can't find the entry in its history that it should be referring to.



            Hope that does it! :D






            share|improve this answer




























              0














              I haven't touched React Native or react-navigation but I'll take a shot!



              It looks like you have index set in the wrong spot.



              Taking a peek at the StackActions and NavigationActions docs, it looks like index belongs in the object you pass to reset rather than navigate. Try switching your code to be like this:





              const reset = StackActions.reset({
              index: 0,
              actions: [
              NavigationActions.navigate({
              routeName: "intervention",
              params: {
              button: true
              }
              })
              ],
              });


              Just as an added funfact, the code you were looking for isn't in your own codebase, rather it comes from the StackRouter.js file from react-navigation. When you run that StackActions.reset action, StackRouter later looks for the new value of index in its internal state. Because index wasn't defined in your code the router can't find the entry in its history that it should be referring to.



              Hope that does it! :D






              share|improve this answer


























                0












                0








                0







                I haven't touched React Native or react-navigation but I'll take a shot!



                It looks like you have index set in the wrong spot.



                Taking a peek at the StackActions and NavigationActions docs, it looks like index belongs in the object you pass to reset rather than navigate. Try switching your code to be like this:





                const reset = StackActions.reset({
                index: 0,
                actions: [
                NavigationActions.navigate({
                routeName: "intervention",
                params: {
                button: true
                }
                })
                ],
                });


                Just as an added funfact, the code you were looking for isn't in your own codebase, rather it comes from the StackRouter.js file from react-navigation. When you run that StackActions.reset action, StackRouter later looks for the new value of index in its internal state. Because index wasn't defined in your code the router can't find the entry in its history that it should be referring to.



                Hope that does it! :D






                share|improve this answer













                I haven't touched React Native or react-navigation but I'll take a shot!



                It looks like you have index set in the wrong spot.



                Taking a peek at the StackActions and NavigationActions docs, it looks like index belongs in the object you pass to reset rather than navigate. Try switching your code to be like this:





                const reset = StackActions.reset({
                index: 0,
                actions: [
                NavigationActions.navigate({
                routeName: "intervention",
                params: {
                button: true
                }
                })
                ],
                });


                Just as an added funfact, the code you were looking for isn't in your own codebase, rather it comes from the StackRouter.js file from react-navigation. When you run that StackActions.reset action, StackRouter later looks for the new value of index in its internal state. Because index wasn't defined in your code the router can't find the entry in its history that it should be referring to.



                Hope that does it! :D







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 16 '18 at 16:25









                Andrew NatoliAndrew Natoli

                262




                262
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53340457%2fundefined-is-not-an-object-evaluating-routesstate-index-key%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Bressuire

                    Vorschmack

                    Quarantine