Solved: First thing is service worker only works in secure mode either in https or localhost. It doesnot work in local resources like file:// or http. and second issue was during registration. navigator.serviceWorkerContainer .register(‘service-worker.js’) .then(function(reg){
The solution is at hand and has been for some years now as this POC clearly testifies. Unfortunately W3C have fought tooth and nail to prevent it from being made available 🙁 Why? I know not. The “cui bono” argument points to plug-in vendors such as Ionic whose whole raison d’etre appears to be background … Read more
You can’t cache POST requests using the Cache API. See https://w3c.github.io/ServiceWorker/#cache-put (point 4). There’s a related discussion in the spec repository: https://github.com/slightlyoff/ServiceWorker/issues/693 An interesting solution is the one presented in the ServiceWorker Cookbook: https://serviceworke.rs/request-deferrer.html Basically, the solution serializes requests to IndexedDB.
This might be a headless Chrome (probably pre-release tests, in case you have it in the Play Store), which does not feature push permission; eg. with Pupeteer, one can only override permissions, but not really accept the permission prompt… and there generally is no desktop attached, where one could push notifications to. Just try and … Read more
No, you can not. Only one service worker per scope is allowed to be registered so the latest kick the previous one out unless the scope is more specific, in this case, the request is attended by the most specific only. Nevertheless, you can attach multiple fetch handlers and they all will process the request … Read more
Thanks to the Pedro Arantes advice, I reached the next working config (see dataGroups and “maxAge”: “0u”): { “index”: “/index.html”, “dataGroups”: [ { “name”: “api”, “urls”: [“/api”], “cacheConfig”: { “maxSize”: 0, “maxAge”: “0u”, “strategy”: “freshness” } } ], “assetGroups”: [ { “name”: “app”, “installMode”: “prefetch”, “resources”: { “files”: [ “/favicon.ico”, “/index.html” ], “versionedFiles”: [ “/*.bundle.css”, … Read more
I believe this is a Chromium bug that has been reported here. Hopefully it will be fixed soon or some more information about the issue will be published. Paul Irish implemented a temporary work around, which is as follows: if (e.request.cache === ‘only-if-cached’ && e.request.mode !== ‘same-origin’) { return; } I ran it inside the … Read more
In general, code that’s outside any event handler, in the “top-level” of the service worker’s global scope, will run each and every time the service worker thread(/process) is started up. The service worker thread may start (and stop) at arbitrary times, and it’s not tied to the lifetime of the web pages it controlled. (Starting/stopping … Read more
After digging deep into this issue, I conclude that there is no support for Service workers in Android as it blocks service workers from HTTP or file protocols. Also the support of Service worker in Ionic framework do not clearly state that it is not supported in hybrid mobile apps. It’s kind of misleading too … Read more
So, considering, you have not posted any code relevant to the service worker, you might consider adding a simple if conditional inside the code block for fetch This code block should already be there inside your service worker.Just add the conditionals self.addEventListener( ‘fetch’, function ( event ) { if ( event.request.url.match( ‘^.*(\/blog\/).*$’ ) ) { … Read more