[Webkit-unassigned] [Bug 199110] New: PWA in iOS use old assets after publish new servicerWorker/assets
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jun 21 10:08:39 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=199110
Bug ID: 199110
Summary: PWA in iOS use old assets after publish new
servicerWorker/assets
Product: WebKit
Version: WebKit Nightly Build
Hardware: iPhone / iPad
OS: iOS 12
Status: NEW
Severity: Critical
Priority: P2
Component: WebKit2
Assignee: webkit-unassigned at lists.webkit.org
Reporter: marlonmleite at gmail.com
This bug is being reported from the bug fix: https://bugs.webkit.org/show_bug.cgi?id=190269
We are currently using iOS 12.3.1 and the new changes in app/.js are publish, but the PWA in iOS load the old assets present in precache.
In Safari it works correctly, but when you're using PWA it does not work. There are behavioral differences between Safari and PWA on iOS.
Our scenario:
- Open the application in Safari;
- We installed PWA on iOS;
- We close the Safari;
- We release a new version of the application;
- PWA continues to use old asset cache - precache (apparently the serviceWorker flow in PWA is different from normal);
- PWA is obsolete and does not update to the new assets in any way;
- We reboot the Iphone and PWA works with the new assets;
This stream works properly on Chrome, Firefox, Android, Safari, but the PWA installed on iOS does not work at all.
My Expectation with PWA in IOS:
Publish a new version of my application and these changes arrive in serviceWorker so that it's possible for my app to force the app to reload to take on new modifications as the behavior it's ok in Android, Chrome, Firefox and so on.
--
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/2cd4c7ed/attachment.html>
More information about the webkit-unassigned
mailing list