[Webkit-unassigned] [Bug 199110] PWA in iOS use old assets after publish new servicerWorker/assets

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=199110

Chris <chrisheaththomas at outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chrisheaththomas at outlook.co
                   |                            |m

--- Comment #10 from Chris <chrisheaththomas at outlook.com> ---
(In reply to youenn fablet from comment #2)
> Thanks for the report.
> IIUC, the PWA is running (Safari is not) while a new version of the
> application is being released.
> The expected behavior is for the PWA service worker to update itself and its
> cache assets as well. This only happens when relaunching the PWA after
> reboot.
> If you do the same flow with Safari, the service worker and its cache assets
> are updated as expected.
> Is that correct?
> 
> If you have a live repro case that you can share (either privately or
> publicly) that may help.

The PWA does not have to be "running while a new version of the application is being released" for this bug to manifest. The PWA just needs to be have been installed (added to the Homescreen). 

Without the workarounds linked by others in the comments, this bug is a blocker to deploying a PWA on iOS.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220429/fe7feef2/attachment-0001.htm>