selfDestroying doesn't destroy the service worker about docs

[Zavim]

I had this same issue. I was able to solve it by removing the site from my history (in my case it was just localhost -- http://127.0.0.1:3000/). There should be something like "remove this site from my history" in the History settings of your browser.

[userquin]

@matthew-dean @Zavim have you read the docs? You MUST not change anything in the configuration, just add selfDestroying: true, check the DANGER entry: https://vite-pwa-org.netlify.app/guide/unregister-service-worker.html

[Zavim]

I hadn't changed anything in the configuration, just removed localhost:3000 from my browser history. Either way, my case was a practice PWA, not client-facing.

[Yankovsky]

I have the same issue and I didn't change anything in the config.

[Yankovsky]

I think of adding a script to GTM to unregister a service worker, bust the cache and refresh the page for the user. Super hacky and ugly, but I am out of options.

[Yankovsky]

I am also trying to play with downgrading vite-plugin-pwa version, because I have a feeling that something was added to the config on the plugin side, and because of that service workers names or something else don't match.

[userquin]

We haven't change anything about the sw name, check it in local without selfDestroying and then add it again, maybe you have some old tests on your local.

Ensure your original sw precache manifest doesn't include the sw itself.

[Yankovsky]

Downgrading from ^0.16.4 to 0.12.8 helped. It worked!

[userquin]

uhmm, I'll check changes between those versions, are you using injectManifest strategy?

[Yankovsky]

Yes, I have the following config:

VitePWA({
        strategies: 'injectManifest',
        registerType: 'autoUpdate',
        injectManifest: {
          maximumFileSizeToCacheInBytes: 5_000_000,
        },
        selfDestroying: true,
      }),

Look, maybe it was something else, I didn't do a thorough investigation.

[Yankovsky]

I had version 0.11.13 installed. Then I updated to the latest version of the plugin and added the flag. It didn't work (or maybe I did something incorrectly). Then I downgraded to 0.12.8 and it worked.