service-worker

I'm trying out the GCM push notification API. So far it works fine, but I'm not sure how to post additional data. I followed the steps on this page: https://developers.google.com/web/fundamentals/getting-started/push-notifications/step-07 So I ended up writing a curl request like this: curl --header "Authorization: key=myKey" --header "Content-Type: application/json" https://android.googleapis.com/gcm/send -d "{\"registration_ids\":[myRegistrationId], \"additionalData\": {\"user_id\":\"1\"}}" And then my sw.js (my service worker) self.addEventListener('push', function(event) { console.log(

I am new to service workers and GAE, I am able to register the service workers but not able to subscribe the PushManager, getting subscription null error. Find the below code for reference. serviceWorkerRegistration.pushManager.getSubscription() .then(function(subscription) { var pushButton = document.querySelector('.js-push-button'); pushButton.disabled = false; if (!subscription) { console.log('subscription error '); return; } console.log('subscriptioned '); // Keep your server in sync with the latest subscriptionId sendSubscriptionToServer(subscription); // Set your UI to show they have

I've built a Progressive Web App that uses caching, but it's unclear to me whether users can (accidentally or on purpose) clear the service worker cache, which may clear my tracking data. When a user clears their browsing data / cookies, this clears all site storage which includes the SW cache, cookies, local storage, indexeddb, and any other local caching system. Furthermore, Ctrl-F5 forces a cache refresh, and is intended to abandon all cached content including service worker cache and just retrieve all content from the servers again. "Clear site data" in Chrome 76 will delete the caches and

Service Worker seems to automatically stop at some point. This behaviour unintentionally closes the WebSocket connection established on activate. When and Why does it stop? How can I programmatically disable this unexpected action to keep Service Worker stay running? What you're seeing is the expected behavior, and it's not likely to change. Service workers intentionally have very short lifespans. They are "born" in response to a specific event ( install , activate , message , fetch , push , etc.), perform their task, and then "die" shortly thereafter. The lifespan is normally long enough that

I have a common serviceworker escenario, where I want catch a notification click and focus the tab where the notification has come from. However, clients variable is always empty, its lenght is 0 console.log("sw startup"); self.addEventListener('install', function (event) { console.log("SW installed"); }); self.addEventListener('activate', function (event) { console.log("SW activated"); }); self.addEventListener("notificationclick", function (e) { // Android doesn't automatically close notifications on click console.log(e); e.notification.close(); // Focus tab if open e.waitUntil(clients

To enable my app running offline. During installation the service worker should: fetch a list of URLs from an async API reformat the response add all URLs in the response to the precache For this task I use Googles Workbox in combination with Webpack. The problem: While the service worker successfully caches all the Webpack assets (which tells me that the workbox basically does what it should), it does not wait for the async API call to cache the additional remote assets. They are simply ignored and neither cached nor ever fetched in the network. Here is my service worker code: importScripts(

I'm trying to use sw-precache , but I must be doing something wrong! I'm mostly using the demo code available from the github repo and can't seem to get updates to the app to come through. Once it's cached the first time, it never checks for new versions. I was expecting that when I publish a new service worker, the browser would request the new service worker and update the cache accordingly in the background. Then using the registration code in the example , I would be able to prompt the user to refresh and get the latest version from their newly refreshed cache. Would really appreciate if