In a Web Application, we use a service-worker
for a few task such as:
We decided to remove Web push feature, this cause the service worker to have a new version.
This is the commit commit.
self.skipWaiting()
}
})
-
- // This will add batch sdk service worker
- self.importScripts(process.env.PUBLIC_URL + '/batchsdk-shared-worker.js')
For some reason, we never go through the event that call skipWaiting()
: https://github.com/pass-culture/pass-culture-app-native/blob/master/src/service-worker.ts#L76
// This allows the web app to trigger skipWaiting via
// registration.waiting.postMessage({type: 'SKIP_WAITING'})
self.addEventListener('message', (event) => {
if (event.data && event.data.type === 'SKIP_WAITING') {
self.skipWaiting()
}
})
This is the state of our app when detecting the new version
If I click on skipWaiting
in the developer tab, then the update perform normally.
On a new release:
self.skipWaiting()
skipWaiting()
(1) works as expected, the skipWaiting()
is called, however, when we are in (2), the release of a new version of our service worker detect the update but skipWaiting()
is never called.
In the case of a new service worker version, how can we call skipWaiting()
to update the service worker automatically ?
When a new app is published, the new service worker automatically detect the new webapp, but it does not install this, for this, you must call sw.skipWaiting()
, either automatically or using a button.
This was working with the following code within the service worker:
self.addEventListener('message', (event) => {
if (event.data && event.data.type === 'SKIP_WAITING') {
self.skipWaiting()
}
})
However, it is working only if the chunks of our application change. In case of a modification of the service worker (and new version of it, not the webapp), then this event is not triggered. I manage to fix this, by adding in our service worker the following:
self.addEventListener('install', () => {
self.skipWaiting()
})
New service worker needs to install and thus emit an install
event.