Buksy’s answer is correct but in my opinion it does not answer the original question, namely: “What can service workers do that web workers cannot? Or vice versa?” There are fundamental differences in their lifecycle and the number of instances per origin you can have. In short: | Web Workers | Service Workers | |————–|————–|——————| … 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
Chrome(or any PWA supporting browser) triggers the beforeinstallprompt event for Web app install banner, which you can catch and re-trigger in more appropriate time when you think user wont miss it/convinced about adding your site to home page. Starting Chrome version 68, catching beforeinstallprompt and handling the install prompt programmatically is mandatory and no banners … Read more
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){
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
After looking at your gist and your question, I think your issue is with scoping. From what I’ve determined with service workers(at least with static files), the service worker only has a maximum scope of the directory it is in. That is to say, it can’t load files/requests/responses that are pulled from a location at … Read more
Applying this change: ‘/service-worker.js’ // ❌ ‘./service-worker.js’ // ✅ fixed my issue. (in navigator.serviceWorker.register(‘/service-worker.js’)) Or maybe you need: ‘%PUBLIC_URL%/serviceworker.js’ Thank @DanielLord for his comment.
Serve your page over HTTPS or use localhost. Service workers require a Secure Context. (MDN page, Chromium page). The value of window.isSecureContext indicates whether [SecureContext] features are visible or hidden. (This is true on a file:// URL and the serviceWorker API will be visible, but it won’t work, of course.)
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
Creating a new request object works as long as you set all the options: // request is event.request sent by browser here var req = new Request(request.url, { method: request.method, headers: request.headers, mode: ‘same-origin’, // need to set this properly credentials: request.credentials, redirect: ‘manual’ // let browser handle redirects }); You cannot use the original … Read more