- Issue created by @JohnTheWriter98
- 🇺🇸United States ChristophWeber
In another Chrome profile you cannot access the service worker from the first profile, nor the manifest. The module should install new instances though, eventually. Still, it is really hard to keep all profile crosstalk at bay, and the maintainers (almost) certainly do not test your scenario, nor make any claims that it will work.
Try a completely separate browser for your test scenario. - Issue was unassigned.
- 🇺🇸United States Doc OConnor
I have the same issue. I do not get a manifest file. I get the service worker, and shows in my dev tools, however, I do not get a manifest file. It is showing a 403 error. Where is the manifest file saved at. I will create one myself. Nice tool, if this would work.
- 🇬🇧United Kingdom Alina Basarabeanu
I can't get it to work.
No manifest.json was generated when enabling the module.
How do I check that the Service Worker is active? I enabled the sub-module pwa_service_worker
I saved the pwa.config.yml file and pushed it to the environment, but the website is unavailable when offline. - 🇬🇧United Kingdom Alina Basarabeanu
In our case, the missing part was the permissions for the anonymous user for 'Access PWA'.
Also, make sure that you enable the sub-module 'pwa_service_worker'. - Status changed to Closed: cannot reproduce
11 months ago 1:52pm 7 February 2024 - 🇩🇪Germany Grevil
@Alina Basarabeanu, note that this issue was created against 1.x instead of 2.x
But yea, I will close this issue for now. If there are further flaws, not already mentioned in the issue queue, feel free to create a new ticket. 8.x-1.x-dev is not supported anymore.