Service worker does not successfully serve the manifest's start_url.
See original GitHub issueThis error is actually pretty hard to fix if you think you are.
At the moment I’m caching the index.html page and I’ve set the start_url to index.html and I still get this error.
I can even go from DevTools > Application > Manifest > start_url
link to the page, switch to offline in network panel and reload the page and get the full page from the service worker.
Any ideas how to debug this?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:17
- Comments:48
Top Results From Across the Web
Service worker does not successfully serve the manifest's ...
My manifest.json has '/' as the start URL and "/" as the scope. The '/' is actually default.aspx which I have cached as...
Read more >Pwa – Service worker does not successfully serve the manifest's ...
My manifest.json has '/' as the start URL and "/" as the scope. The '/' is actually default.aspx which I have cached as...
Read more >Web Application Manifest - W3C
The manifest's start_url member is a string that represents the start URL , which is URL that the developer would prefer the user...
Read more >Using Service Workers - Web APIs | MDN
If successful, the service worker is executed in a ServiceWorkerGlobalScope ; this is basically a special kind of worker context, running off ...
Read more >`start_url` does not respond with a 200 when offline
Lighthouse flags web apps whose start URL doesn't respond with a 200 ... When offline, use the service worker as a network proxy...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@frlinw we totally agree! on latest LH I don’t see any of those issues on your site though so hopefully fixed in the past couple months 👍
@wdiechmann there is such an option in devtools -> application tab. This option is handy while developing and ignoring the Service Worker but it has nothing to do with Lighthouse itself.
@Drag13 I get a 404 on http://makephoto.azurewebsites.net/manifest.json or https://makephoto.azurewebsites.net/manifest.json
you can see if the manifest gets loaded correctly in the application tab