angular-pwa

问题 I've created an Angular PWA application and built it by running: ng build --prod . It has built the production ready application successfully. I've ran the built application in local by running command: http-server -o , It was running as expected. Problem: When I've deployed in production's server tomcat apache webapp directory and ran it I am getting: Service worker is not registered or does not control the Start URL . Service worker is not registering in my production environment. Please

问题 When I serve the web-app on port 3330, I can make the webapp working on port 3333 using --proxy ./src/proxy.config.json, but I don't know how to make http-server to make to work at the same way "start": "ng serve -o --port 3330 --watch --proxy-config ./src/proxy.config.json", "pwa": "http-server -p 8080 -c-1 dist/satoshi-pwa --proxy http://localhost:3333", proxy.config.json: { "/api": { "target": "http://localhost:3333", "secure": false, "changeOrigin": true, "pathRewrite": { "^/api": "/" } }

问题 In an Angular (8) app I'd like to add a custom offline page (just a plain simple html-file to begin with). I have set up my app as a PWA (using @angular/pwa and configured everything so that it at least works smoothly while being online). However, I've had a hard time making updates available for PWA users. So, after many hours of try and error I decided to exclude index.html from the ngsw-config.json . This has -of course- the effect that index.html gets loaded every single time (not so bad,

问题 With localhost Angular PWA service worker works fine in all scenarios, BUT After deployment (on Azure server with GIT pipeline), In Online mode all works fine: 1. Service Worker is registered. 2. API responses are cached. Now when i go offline, the service worker still tries to fetch the api response from Network( and give 504 error since its offline mode) INSTEAD of taking those responses from CACHE. I can see the data there in cache, But the problem is that ServiceWorker still tries to

问题 With localhost Angular PWA service worker works fine in all scenarios, BUT After deployment (on Azure server with GIT pipeline), In Online mode all works fine: 1. Service Worker is registered. 2. API responses are cached. Now when i go offline, the service worker still tries to fetch the api response from Network( and give 504 error since its offline mode) INSTEAD of taking those responses from CACHE. I can see the data there in cache, But the problem is that ServiceWorker still tries to

问题 I am working on an angular PWA application. So I added an npm package by ng add @angular/pwa . It is added successfully with no errors. The generated Manifest is working fine. But I am facing issues with the service worker. When the application goes online it stores all the caches (see attachment) but whenever the application goes offline, instead of serving the request from the service worker it shows the error - HTTP ERROR 504 Here is my ngsw-config.json - { "index": "/index.html",

问题 I am working on an angular PWA application. So I added an npm package by ng add @angular/pwa . It is added successfully with no errors. The generated Manifest is working fine. But I am facing issues with the service worker. When the application goes online it stores all the caches (see attachment) but whenever the application goes offline, instead of serving the request from the service worker it shows the error - HTTP ERROR 504 Here is my ngsw-config.json - { "index": "/index.html",

问题 I created an angular app which I pushed to my Bitbucket repository. To turn my angular app into a Progressive Web App, I followed this step by step guide. The result, was a newly created folder (as per the guide) called angular-pwa . I then cd into the angular-pwa and pulled my app from the repository. The commands I used to pull my app: git init . git remote add origin https://myName@bitbucket.org/myName/myAppName.git git pull origin master I never saw any error messages following the above

问题 I've built a PWA using angular 6 and the @angular/pwa package. I've been trying to fix this but no matter what I do, I'm getting the start_url error. I have tried: Using absolute links Making sure the start_url is within the SW's scope (sw is in the main folder) Using the filename "/index.html" as I've seen in other support threads here. Clearing all browser history and cache everytime. Searching through Github issues on the @angular/pwa package Searching google in general for this PWA issue.

问题 I think we found a regression in iOS 13.2/13.3 in regard to PWAs running in standalone mode. Since on iOS PWA cannot access getUserMedia() we rely on the capture attribute on the HTML5 input tag to let the user take a picture and send it to a server. Our code looks like this: <div class="camera-upload"> <input type="file" class="hidden" name="uploadPhotoInput" accept="image/*" capture="environment" (change)="onTakePhoto($event)"> <button type="button" class="btn btn-primary">Take photo<