service-worker

I'm using the recently release FCM messaging support for push notifications on the chrome. When my app is in the background, I get the notification but nothing happens when I click the notification. How to I specify the URL which should open when the user clicks the notification? (I understand how its done using the pure service worker concept using the notificationclick event, I want to know how to do that using FCM messaging .) messaging.setBackgroundMessageHandler(function(payload) { var data = payload || {}; var shinyData = decoder.run(data); console.log('[firebase-messaging-sw.js]

I work with angularjs and use service worker to receive push notification. but navigator.serviceWorker.controller is null until page refresh,and I don't know how to do to solve this problem some code of serviceworker : self.addEventListener('push', pwServiceWorker.pushReceived); self.addEventListener('notificationclick', pwServiceWorker.notificationClicked); // refresh caches self.addEventListener('activate', function (event) { event.waitUntil( caches.keys().then(function (cacheNames) { return Promise.all( cacheNames.map(function (cacheName) { return caches.delete(cacheName); }) ); }) ); });

I have a service worker installed in my website, everything works fine, except when I push an update to the cached files, in fact; they stay catched forever and I seem to be unable to invalidate the cache unless I unsubscribe the worker from the `chrome://serviceworker-internals/ const STATIC_CACHE_NAME = 'static-cache-v1'; const APP_CACHE_NAME = 'app-cache-#VERSION'; const CACHE_APP = [ '/', '/app/app.js' ] const CACHE_STATIC = [ 'https://fonts.googleapis.com/css?family=Roboto:400,300,500,700', 'https://cdnjs.cloudflare.com/ajax/libs/normalize/4.1.1/normalize.min.css' ] self.addEventListener(

What are the core differences between service worker and AppCache. What are the pros and cons of each and when to prefer one over another . The primary difference is that AppCache is a high-level, declarative API, with which you specify the set of resources you'd like the browser to cache; whereas Service Worker is a low-level, imperative, event-driven API with which you write a script that can intercept fetch events and cache their responses along with doing other things (like displaying push notifications). The pros and cons are largely a function of API design: theoretically, AppCache is

I have the problem that after registering the serviceWorker the navigator.serviceWorker.controller is always null. I never do a force refresh and just refresh the page. I test it with Google Chrome 42.0.2311.152 m (32-Bit). var currentServiceWorker = null; navigator.serviceWorker.register(SERVICE_WORKER_URL).then(function(serviceWorkerRegistration { if (navigator.serviceWorker.controller) { currentServiceWorker = navigator.serviceWorker.controller; } else { currentServiceWorker = serviceWorkerRegistration.active; } }); According to this: The controller read-only property of the

I am implementing PWA into my project, I have setted up the serviceworker.js, and I am using workbox.js for cache routing and strategies. 1- I add the offline page to cache on install event, when a user first visit the site: /** * Add on install */ self.addEventListener('install', (event) => { const urls = ['/offline/']; const cacheName = workbox.core.cacheNames.runtime; event.waitUntil(caches.open(cacheName).then((cache) => cache.addAll(urls))) }); 2- Catch & cache pages with a specific regex, like these: https://website.com/posts/the-first-post https://website.com/posts/ https://website.com

I'm trying to implement part of app with PWA approach, that works fine on Android , but not for iOS . We need to have offline content availability option to update content dynamically (like special offers or so). With service worker we show prompt to update web content. As were mentioned here service workers are not supported within WKWebView (or UIWebView ). So is there analog or alternative solution like smart cache control? Seems like it is possible to store some web content from app and be able to update it if something changes. May there is already a framework/library/approach for that