Updated handler of service worker keeps being triggered on android after refresh












0















I'm using register-service-worker to handle detecting when there's an update to the PWA. The source of the service worker is minimal.



My handling code is like that:



if (process.env.NODE_ENV === 'production') {
register(`${process.env.BASE_URL}service-worker.js`, {
ready() {
console.log(
'App is being served from cache by a service worker',
);
},
cached() {
console.log('Content has been cached for offline use.');
},
updated() {
console.log('New content is available; please refresh.');
store.commit("updateAvailable");
},
offline() {
console.log('No internet connection found. App is running in offline mode.');
},
error(error) {
console.error('Error during service worker registration:', error);
},
});
}


store.commit("updateAvailable"); shows a modal telling the user to refresh, where one click on the refresh button triggers location.reload(true). I also tried location.reload().



On desktop, there's no issues. On android, in the chrome browser, the update notification keeps popping up, even if I refresh / keep refreshing. I need to change the url location to another website and then go back to the app for the update to go through and the notification to stop popping up.



I added the update mechanism in a minimal webapp (in the refresh-test branch) I own to reproduce the problem. The problem can be reproduced in my android chrome by:




  • Deploying the app

  • Going on the app on android chrome

  • Making a minimal change on the app and rebuilding it

  • On android chrome, refresh the page


The "App is updated, refresh" alert will show and keep being shown every refresh. The problem does not happen on desktop, one refresh is enough to update the app.



Is there any reason the service worker behaves differently on mobile/android? Is there anything I can try to fix the problem? I already tried calling skipWaiting() in the service worker before refreshing the page.



I'm using chrome 69.0.3497.100 / Android 7.0.0 if that makes any difference.










share|improve this question



























    0















    I'm using register-service-worker to handle detecting when there's an update to the PWA. The source of the service worker is minimal.



    My handling code is like that:



    if (process.env.NODE_ENV === 'production') {
    register(`${process.env.BASE_URL}service-worker.js`, {
    ready() {
    console.log(
    'App is being served from cache by a service worker',
    );
    },
    cached() {
    console.log('Content has been cached for offline use.');
    },
    updated() {
    console.log('New content is available; please refresh.');
    store.commit("updateAvailable");
    },
    offline() {
    console.log('No internet connection found. App is running in offline mode.');
    },
    error(error) {
    console.error('Error during service worker registration:', error);
    },
    });
    }


    store.commit("updateAvailable"); shows a modal telling the user to refresh, where one click on the refresh button triggers location.reload(true). I also tried location.reload().



    On desktop, there's no issues. On android, in the chrome browser, the update notification keeps popping up, even if I refresh / keep refreshing. I need to change the url location to another website and then go back to the app for the update to go through and the notification to stop popping up.



    I added the update mechanism in a minimal webapp (in the refresh-test branch) I own to reproduce the problem. The problem can be reproduced in my android chrome by:




    • Deploying the app

    • Going on the app on android chrome

    • Making a minimal change on the app and rebuilding it

    • On android chrome, refresh the page


    The "App is updated, refresh" alert will show and keep being shown every refresh. The problem does not happen on desktop, one refresh is enough to update the app.



    Is there any reason the service worker behaves differently on mobile/android? Is there anything I can try to fix the problem? I already tried calling skipWaiting() in the service worker before refreshing the page.



    I'm using chrome 69.0.3497.100 / Android 7.0.0 if that makes any difference.










    share|improve this question

























      0












      0








      0








      I'm using register-service-worker to handle detecting when there's an update to the PWA. The source of the service worker is minimal.



      My handling code is like that:



      if (process.env.NODE_ENV === 'production') {
      register(`${process.env.BASE_URL}service-worker.js`, {
      ready() {
      console.log(
      'App is being served from cache by a service worker',
      );
      },
      cached() {
      console.log('Content has been cached for offline use.');
      },
      updated() {
      console.log('New content is available; please refresh.');
      store.commit("updateAvailable");
      },
      offline() {
      console.log('No internet connection found. App is running in offline mode.');
      },
      error(error) {
      console.error('Error during service worker registration:', error);
      },
      });
      }


      store.commit("updateAvailable"); shows a modal telling the user to refresh, where one click on the refresh button triggers location.reload(true). I also tried location.reload().



      On desktop, there's no issues. On android, in the chrome browser, the update notification keeps popping up, even if I refresh / keep refreshing. I need to change the url location to another website and then go back to the app for the update to go through and the notification to stop popping up.



      I added the update mechanism in a minimal webapp (in the refresh-test branch) I own to reproduce the problem. The problem can be reproduced in my android chrome by:




      • Deploying the app

      • Going on the app on android chrome

      • Making a minimal change on the app and rebuilding it

      • On android chrome, refresh the page


      The "App is updated, refresh" alert will show and keep being shown every refresh. The problem does not happen on desktop, one refresh is enough to update the app.



      Is there any reason the service worker behaves differently on mobile/android? Is there anything I can try to fix the problem? I already tried calling skipWaiting() in the service worker before refreshing the page.



      I'm using chrome 69.0.3497.100 / Android 7.0.0 if that makes any difference.










      share|improve this question














      I'm using register-service-worker to handle detecting when there's an update to the PWA. The source of the service worker is minimal.



      My handling code is like that:



      if (process.env.NODE_ENV === 'production') {
      register(`${process.env.BASE_URL}service-worker.js`, {
      ready() {
      console.log(
      'App is being served from cache by a service worker',
      );
      },
      cached() {
      console.log('Content has been cached for offline use.');
      },
      updated() {
      console.log('New content is available; please refresh.');
      store.commit("updateAvailable");
      },
      offline() {
      console.log('No internet connection found. App is running in offline mode.');
      },
      error(error) {
      console.error('Error during service worker registration:', error);
      },
      });
      }


      store.commit("updateAvailable"); shows a modal telling the user to refresh, where one click on the refresh button triggers location.reload(true). I also tried location.reload().



      On desktop, there's no issues. On android, in the chrome browser, the update notification keeps popping up, even if I refresh / keep refreshing. I need to change the url location to another website and then go back to the app for the update to go through and the notification to stop popping up.



      I added the update mechanism in a minimal webapp (in the refresh-test branch) I own to reproduce the problem. The problem can be reproduced in my android chrome by:




      • Deploying the app

      • Going on the app on android chrome

      • Making a minimal change on the app and rebuilding it

      • On android chrome, refresh the page


      The "App is updated, refresh" alert will show and keep being shown every refresh. The problem does not happen on desktop, one refresh is enough to update the app.



      Is there any reason the service worker behaves differently on mobile/android? Is there anything I can try to fix the problem? I already tried calling skipWaiting() in the service worker before refreshing the page.



      I'm using chrome 69.0.3497.100 / Android 7.0.0 if that makes any difference.







      android vue.js progressive-web-apps






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 24 '18 at 2:04









      coyotte508coyotte508

      4,48132050




      4,48132050
























          0






          active

          oldest

          votes











          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%2f53454592%2fupdated-handler-of-service-worker-keeps-being-triggered-on-android-after-refresh%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f53454592%2fupdated-handler-of-service-worker-keeps-being-triggered-on-android-after-refresh%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

          Create new schema in PostgreSQL using DBeaver

          Deepest pit of an array with Javascript: test on Codility

          Costa Masnaga