lighthouse: Audit claims start_url of /?utm_ is not cached when navigateFallback exists
In my manifest I specify start_url as something with utm_ params (as suggested by https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/#set_a_start_url):
"start_url": "/?utm_source=homescreen"
My SW precaches index.html and serves it as navigateFallback (as generated by sw-precache), but Lighthouse doesn’t seem to recognize this and fails the audit with “Failures: Manifest start_url is not cached by a Service Worker.”
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 10
- Comments: 18 (6 by maintainers)
Looks like 709 is still open. What’s the plan on this one?
@abdonrd it’s been prioritized and will be unblocked when the work for #709 has been completed.
Unfortunately I don’t have a test URL handy (since I changed the start_url of what I’m working on back to
/to pass this test). RE that tradeoff though, IMO as long as the app developer provides an offline fallback, it means that they put some thought into the offline use case so I think they should pass anyways.