iOS 17 Safari / PWA web app issues

Hi,

We are developing a web application that was working fine until iOS version 16.6.1, both in Safari and PWA mode. However, visitors that have iOS 17 installed experience some kind of caching issues. For your information, our web application is built with Angular and upon opening you're presented with a pulsing logo, and afterwards with either the homepage or a login screen, depending on the session.

If you just updated to iOS 17 and have the PWA already installed, upon opening the PWA nothing is shown, except for a question mark replacing the logo. Nothing is happening anymore. The only thing to get it back to work, is to open the page in Safari, almost like it needs the Safari cache to contain the necessary files.

But here comes the strange part: After closing Safari (remove it from the task manager) with our website opened in one tab, my cache still holds the files from our web app, but the PWA will still fail to load properly. If you would now open Safari, even the 'old' open tab will show the same behavior as the PWA. Refreshing the page will fix this most of the time (but not always). Closing and opening the PWA application again will then work usually (also: not always).

Sometime while refreshing, FetchEvent.respondWith runs into an TypeError (Internal error).

Does anyone run into the same issue or know how to fix this?

Thanks in advance!

We are experiencing the same issue.

Exact error in Safari we are getting some times is:

Safari can't open the page. There error was: "FetchEvent.respondWith received an error: TypeError: Internal error".

We are experiencing the exact same issue here. Angular 16 + Ionic 6.5. Any sign of a fix?

lots of complaits from our users as well, when opening our website:

The very same issue here. There is a github issue against Angular here which includes a partial workaround: https://github.com/angular/angular/issues/50378 With this workaround, offline mode is still broken, but at least the apps reliably loads again if there is internet access and serves (most)? of its assets from the cache.

There is a workaround in the Angular GitHub repo's issue list. It has worked for us

https://github.com/angular/angular/issues/50378#issuecomment-1716430091

I hope this helps you.

Definitely seeing issues with PWA under iOS 17, but we unfortunately have a much older app with AngularJS. It seems like the entire app just loses connection to its IndexedDB, and returns to the login screen, whereupon it uses LocalStorage info to log back in again. After looping in this process a few times, then LocalStorage gets wiped and the user has to login from scratch. Just terrible!

Does this means the bug is fixed in 17.2?

https://developer.apple.com/documentation/safari-release-notes/safari-17_2-release-notes

Fixed a cache miss bug in DOMCache that triggered service worker fetch errors. (115740959) (FB13188943) I'm also getting the same problem but it's in WKWebView loading Angular App. Does WKWebView problem also going to be fixed from above bug fix in 17.2?

I am the developer of FindMeSAR (https://findmesar.com). This open source PWA is written in plain javascript and uses a service worker that has a fetch listener. Works fine in iOS 16. Throws a service worker error in iOS 17.

Anyone can try this for themselves by browsing to findmesar.com and follow the installation instructions on the screen.

I am also faced the same issue in my website, which has service worker enabled it blocked GTM url from safari browser after ios 17.1.2 update. Is there any work around ?

Same here, since iOS 17 our Vue PWA App is showing empty components. Before 17 it worked fine.

iOS 17 Safari / PWA web app issues
 
 
Q