Just faced the same problem: Chrome is not happy with background.scripts and insists on using background.service_worker Firefox doesn’t support background.service_worker and wants background.scripts Manifest v3 is developed by Google, so looks like Firefox team haven’t fully implemented it yet. Firefox 109 is the first version to “support” manifest v3 (released on January 17). I was … Read more
What you’re seeing is the expected behavior, and it’s not likely to change. Service workers intentionally have very short lifespans. They are “born” in response to a specific event (install, activate, message, fetch, push, etc.), perform their task, and then “die” shortly thereafter. The lifespan is normally long enough that multiple events might be handled … Read more
TL;DR: I’ve identified at least two issues causing breakage in my case; you can use this build script for now to try my fix, and see the app work offline here. Further testing & pull requests needed. While I’ve been unable to find a documented answer, here’s what I’ve been able to find thus far, … Read more
You can use the chrome devtools, and under Application>Service Workers path select the Update on refresh checkbox You can also use the Bypass for network checkbox to avoid Service worker’s register event form firing.
Did you check the cookie setting in about:preferences#privacy, it must be ‘keep until they expire’, if you have ‘keep until I close firefox’ selected sw will not register. you can find details on this thread: https://bugzilla.mozilla.org/show_bug.cgi?id=1429714
Type this in the address bar of Firefox and deregister the service workers you want. about:debugging You can scroll down to Service Workers section or find using Ctrl+f or Cmd+f for that text.
Yes you should cache your manifest.json file, because if you a building a PWA, then it must have a functionality to Add to home screen. In your manifest file, it contains a start_url that needs to be cached by service worker and should return a 200 response when offline. Let’s assume anyone is offline browsing … Read more
First thing to say is this depends somewhat on the platform. My understanding of chrome is: On desktop platforms like windows and Mac OS X the browser needs to have some background process running for a service worker to be able to run. On Mac OS X this is quite easy to detect as the … Read more
navigator.onLine and the related events can be useful when you want to update your UI to indicate that you’re offline and, for instance, only show content that exists in a cache. But I’d avoid writing service worker logic that relies on checking navigator.onLine. Instead, attempt to make a fetch() unconditionally, and if it fails, provide … Read more