You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expose a route /client/version on express server. This route output a simple result :
{"version": "X.Y.Z"}
If when comparing this version value with current one of active client we detect a change, we must start an upgrade process. This update process should not be automatic and displayed to user for validation.
Upgrade process when started must take care of cleaning correctly local cache of previous version
the release has been published before the app (re)load
In first scenario we can notify the user that a new version is available (that's why I talk about a notification) and when the user click upgrade, it simply reload the app.
That brings us to the 2nd scenario, in case of a reload, the actual offline tool (that enables PWA) should use the network and clear the cache.
It looks like this doesn't work correctly.
cf. https://twitter.com/NokiDev/status/1137338344256528384
when a new version is available, the app cannot be upgraded from a pwa or mobile browser like brave or FF.
The text was updated successfully, but these errors were encountered: