Closed FiratUsta closed 6 months ago
This needs to be solved for 2.0.0 release.
All testing shows this is fixed with 11e8140 , however for it to take effect users on v1.3.1 will have to clear caches manually and/or reinstall their PWAs.
For the official instance, this should be fine when the project migrates to its own domain.
Closing for now, may reopen if I encounter any other issues.
Currently there are some issues regarding the service worker with the updates. It's supposed to erase old caches and replace them with new files on an update but nothing short of manually deleting old caches seem to work and users might be stuck on earlier versions.
This needs to be investigated and solved.