Why is onDestroyView in a fragment called immediately after navigating with JetPack Navigation












0















Is it normal behaviour that onDestroyView() is called immediately when you navigate to a different fragment?



I call the following method to navigate:



findNavController().navigate(R.id.action_homefragment_to_detailsfragment)


Is there a way to avoid this? Or should everything be restored from a ViewModel? For example my last scroll position in a ScrollView..










share|improve this question





























    0















    Is it normal behaviour that onDestroyView() is called immediately when you navigate to a different fragment?



    I call the following method to navigate:



    findNavController().navigate(R.id.action_homefragment_to_detailsfragment)


    Is there a way to avoid this? Or should everything be restored from a ViewModel? For example my last scroll position in a ScrollView..










    share|improve this question



























      0












      0








      0








      Is it normal behaviour that onDestroyView() is called immediately when you navigate to a different fragment?



      I call the following method to navigate:



      findNavController().navigate(R.id.action_homefragment_to_detailsfragment)


      Is there a way to avoid this? Or should everything be restored from a ViewModel? For example my last scroll position in a ScrollView..










      share|improve this question
















      Is it normal behaviour that onDestroyView() is called immediately when you navigate to a different fragment?



      I call the following method to navigate:



      findNavController().navigate(R.id.action_homefragment_to_detailsfragment)


      Is there a way to avoid this? Or should everything be restored from a ViewModel? For example my last scroll position in a ScrollView..







      android android-architecture-components android-jetpack






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 26 '18 at 16:06







      Luciano

















      asked Nov 26 '18 at 15:55









      LucianoLuciano

      1,60842650




      1,60842650
























          1 Answer
          1






          active

          oldest

          votes


















          2














          Fragments on the back stack have their views destroyed, but the view state is saved and automatically restored when it comes to the top of the stack again (i.e., you hit the system back button).



          Only views with an android:id have their state saved and restored, so make sure any important views have an id.






          share|improve this answer
























          • Thanks, you're right. I didn't know about views need to have an id to get auto restored.

            – Luciano
            Nov 27 '18 at 7:22











          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%2f53484790%2fwhy-is-ondestroyview-in-a-fragment-called-immediately-after-navigating-with-jetp%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









          2














          Fragments on the back stack have their views destroyed, but the view state is saved and automatically restored when it comes to the top of the stack again (i.e., you hit the system back button).



          Only views with an android:id have their state saved and restored, so make sure any important views have an id.






          share|improve this answer
























          • Thanks, you're right. I didn't know about views need to have an id to get auto restored.

            – Luciano
            Nov 27 '18 at 7:22
















          2














          Fragments on the back stack have their views destroyed, but the view state is saved and automatically restored when it comes to the top of the stack again (i.e., you hit the system back button).



          Only views with an android:id have their state saved and restored, so make sure any important views have an id.






          share|improve this answer
























          • Thanks, you're right. I didn't know about views need to have an id to get auto restored.

            – Luciano
            Nov 27 '18 at 7:22














          2












          2








          2







          Fragments on the back stack have their views destroyed, but the view state is saved and automatically restored when it comes to the top of the stack again (i.e., you hit the system back button).



          Only views with an android:id have their state saved and restored, so make sure any important views have an id.






          share|improve this answer













          Fragments on the back stack have their views destroyed, but the view state is saved and automatically restored when it comes to the top of the stack again (i.e., you hit the system back button).



          Only views with an android:id have their state saved and restored, so make sure any important views have an id.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 26 '18 at 17:08









          ianhanniballakeianhanniballake

          104k15216230




          104k15216230













          • Thanks, you're right. I didn't know about views need to have an id to get auto restored.

            – Luciano
            Nov 27 '18 at 7:22



















          • Thanks, you're right. I didn't know about views need to have an id to get auto restored.

            – Luciano
            Nov 27 '18 at 7:22

















          Thanks, you're right. I didn't know about views need to have an id to get auto restored.

          – Luciano
          Nov 27 '18 at 7:22





          Thanks, you're right. I didn't know about views need to have an id to get auto restored.

          – Luciano
          Nov 27 '18 at 7:22




















          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%2f53484790%2fwhy-is-ondestroyview-in-a-fragment-called-immediately-after-navigating-with-jetp%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

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Calculate evaluation metrics using cross_val_predict sklearn

          Insert data from modal to MySQL (multiple modal on website)