progressive-web-apps

问题 I have built a SPA that works in the browser in that on load it provides an auth option, I click google signin and the firebase auth flow continues until I have an auth token etc. I can then switch the PWA and use as normal. But if I then logout, I cannot log back in again with the App using Google Auth - whether I let the google signin popup run in the App or in Chrome, no confirmation ever gets abck to the App and indeed it seems to crash. The issue has something to do with the loading of

问题 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. 回答1: 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. 回答2: Furthermore, Ctrl-F5 forces a cache refresh, and is intended to abandon all cached content including service worker

问题 Hey I am trying to program my first pwa and got the following problem: when I start my web app I get the following error: Site cannot be installed: no matching service worker detected. You may need to reload the page, or check that the service worker for the current page also controls the start URL from the manifest I think my manifest url is right because of this link manifest.json "start_url": ".", "display": "standalone", "orientation": "portrait", "theme_color": "#29BDBB", "background

问题 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

问题 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

问题 Is there any method to open website (PWA) urls in the installed PWA in iOS- Safari? Use case: I'm sending email links to login in my PWA, how can I make this url's open directly with the installed PWA instead of the browser? 回答1: 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

问题 I'm struggling to create a simple POC for iOS PWA with a small video. https://test-service-worker.azurewebsites.net/ I have simple service worker registration and I cache a small (700kB) video. When I'm online the page works just fine. When I turn on airplane mode and go offline, the page is still reloaded but video will not play. This POC is based on Google Chrome example https://googlechrome.github.io/samples/service-worker/prefetch-video/ The video from this example will not work in iOS

问题 In app.js , I am checking the serviceWorker existence in navigator object and if available then registering the SW. if ('serviceWorker' in navigator) { navigator.serviceWorker.register('./service-worker.js', { scope: './' }) .then(function(registration) { console.log("Service Worker Registered!"); }).catch(function(err) { console.log("Service Worker not registered!", err); }); } When trying to register SW, I receive the below error in Firefox. I also made sure the service-worker.js file is

问题 I am trying to implement PWA in standalone mode on Android and iOS. I have a secure node.js server (HTTPS) and everything is apparently working fine (index.html, manifest.json, serviceWorker.js, ...). The application runs correctly from Chrome and can be added to the home screen and run in standalone mode on the PC. It also works in standalone mode on iOS (Safari), but not on Android (Chrome). Because of this, I tested three different PWAs: with a basic example of ionicPWA, another example of

问题 I have two subdomains: https://abc.xxxx.com and https://xyz.xxxx.com. So my questions: 1). is it possible to register a service worker for https://xyz.xxxx.com from https://abc.xxxx.com ? if yes then how? 2). if http://abc.xxxx.com ( http insecure) then anyway to register a service worker for https://xyz.xxxx.com from http://abc.xxxx.com like in iframe or something.... This is a real situation, I am facing for my multiple subdomain. Any help appreciated. Thanks in advance. 回答1: Here are some