Jeff Posnick

@evdama: A complication around support for `localStorage` is that it can't be accessed from inside of a service worker. So if we did support clearing it, that would only work...

There's a [bug](https://bugs.webkit.org/show_bug.cgi?id=182444) in Safari's service worker implementation that prevented resources loaded by `importScripts` from being implicitly cached, as the service worker specification requires. This has been [fixed](https://webkit.org/blog/8332/release-notes-for-safari-technology-preview-59/) in Safari...

Here's what seems to be the relevant, underlying bug in Safari: https://bugs.webkit.org/show_bug.cgi?id=190269 I'm going to leave this tracking bug against Workbox open for the time being, and we should loop...

If folks on the latest iOS release still can reproduce issues, let us know and we can reopen.

I believe that the existing service worker registration and cache isn't shared when an app goes from being loaded in Safari to standalone on the iOS homescreen, but after you...

https://www.tiktok.com/ uses Workbox and has a custom offline experience, and when I just tried adding it to my homescreen using the most current iPad version of Safari, I was able...

Hello @akaFTS—if this issue is limited to iOS Safari, then I'd recommend taking advantage of the offer at https://twitter.com/jensimmons/status/1491113783838019584 I.e. file a bug with steps to reproduce at https://bugs.webkit.org/, and...

This should be resolved in https://github.com/GoogleChrome/sw-precache/releases/tag/3.2.0. Can you confirm?

Sorry for the misinformation re: https://github.com/GoogleChrome/sw-precache/releases/tag/3.2.0 I think I see what's going on, and it should be able to work around this if you use the `urlPattern` option to match...

Hello @andyrichardson! I am not sure that your diagnosis of what's going on is accurate. Calling `respondWith(responsePromise)` on a `FetchEvent` already extends the lifetime of the service worker until `responsePromise`...