You cannot access localStorage (and also sessionStorage) from a webworker process, they result will be undefined, this is for security reasons. You need to use postMessage() back to the Worker’s originating code, and have that code store the data in localStorage. You should use localStorage.setItem() and localStorage.getItem() to save and get data from local storage. … Read more
For the first exception:- Uncaught (in promise) TypeError: Failed to execute ‘Cache’ on ‘addAll’: Request failed You get this exception when any files which you have mentioned in your cache list return a 404 response. So make sure the all the resources are giving 200. For the 2nd error:- start_url does not respond with a … Read more
Go to chrome://serviceworker-internals Choose any service worker and start it if not already started. Click on Inspect!! Boom! You have the console there!
In my case this error occurred seemingly at random. One moment it was working, and the next moment it wasn’t. Known working commits were also broken. I had to delete node_modules and reinstall them which fixed the problem.
A service worker has additional functionality beyond what’s available in shared workers, and once registered, they persist outside the lifespan of a given web page. Service workers can respond to message events, like shared workers, but they also have access to additional events. Handling fetch events allows service workers to intercept any network traffic (originating … Read more
As I figured out, this question is really only related to beginners in PWA, which don’t know that you can (and need) to configure PWA for achieving this. If you feel addressed now (and using VueJS) remember: To automatically download the new content, you need to configure PWA. In my case (VueJS) this is done … Read more
Please find below the cause for your specific issue and the cause for not getting the details of failure in the console log. Before Chrome 93, the service worker file must be in the root path where manifest.json is. This is a limitation of Service Worker specification, relaxed for extensions since Chrome 93. If, for … Read more
If you are using Chrome in Android or any of the desktop OS, that would be the default behavior. Check on “Android intent filter” in this link. This feature is not supported in iOS yet for PWA apps(created using Safari- the only option for iOS as of June-2018).See “What PWAs can do on Android and … Read more
Although Ian’s answer was great by the time it was posted (04.2015), this question became important point of entry for a lot people interested in service workers and Progressive Web Apps and answer is much broader now. Feedback from Apple 30.03.2018: Service workers are shipped with Safari 11.1. Good job! https://developer.apple.com/library/content/releasenotes/General/WhatsNewInSafari/Articles/Safari_11_1.html 20.12.2017: Service workers enabled … Read more
You mention that you have service-worker.js in the same directory as app.js, but the URL passed to .register() is relative to the HTML document’s path. You need to make sure your service-worker.js file is in the same directory as the .html file corresponding to the page you’re on.