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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 21 13:41:24 PDT 2019


--- Comment #3 from Marlon Maxwel <marlonmleite at gmail.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.

Yes correct, in Safari the service worker and its cache assets are updated as expected.

In Android, the PWA don't require a phone reboot to apply new release/assets. This is good for user receive new released version/assets with more frequency. And this is good idea for iOS users with PWA.

I will recreate this scenario as soon as possible and publish it here. Because my app it's in homologation and not available for the public access in the moment, only in my company.

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/20190621/a8feba5b/attachment-0001.html>

More information about the webkit-unassigned mailing list