Why is my app / website does not update to latest version?

Hey all!

Before starting, if you want to ask the question about a missing set, please first check that you are on the latest version :)

UrzaGatherer is based on Service Workers and sometimes they could be stubborn :)

First things to check:

* Close the app/browser completely (Kill it!!)

* Start the app/browser and go to settings and in the Database section click on Update Database button and restart

If this is not working, here is a procedure to follow to force update (based on your browser. Please note that Android app is based on Chrome):

How to force update a service worker on Chrome, Firefox and Safari?

23 comments

23 Comments

David Catuhe

Dec 12

ok just published 14.0.3 with hopefully a fix (there is nothing server side with service worker so the bug is for sure in my code)

Stephen Wicklund

Dec 12

Replying to

Okay, I tried updating to 14.0.3, and seeing if it still places the js/data files in the images cache.

First I did a full cache clear:

Deleted all collections under "DevTools -> Application -> Cache storage".
Enabled the "Disable cache" checkbox in "DevTools -> Network".
Held down the page-reload button (with dev-tools opened), and pressed "Empty Cache and Hard Reload".

The app then updated to 14.0.3 (and stays that way even after regular refreshes/page-loads now -- which is as expected / basically my normal update process).

I then inspected the images cache, and indeed, only image files are stored there now! I'll have to wait for the next app update to be 100% sure that this variant of the update issue is fixed, but so far it seems to be.

That said, I should note that the approach used to fix that caching bug appears to also result in the "db.data" file not getting cached anywhere (the "urzagatherer-vXXXX" cache collection is not getting created). So, even when I do a normal load/reload of the page (ie. with "Disable cache" disabled, and dev-tools panel not open), my browser is downloading the entire "db.data" file again, which amounts to about 95mb of extra load on the server (and waiting in my browser) each time I load the page.

Now from my perspective, this is still an improvement over the old issue (of app updates not showing up). But, I imagine it's not ideal from your perspective, since it means your server might start getting hammered with a lot of unnecessary re-downloads of the db.data file (due to not getting cached anywhere), plus might cause issues for users trying to access the app/site over mobile data.

Let me know if further help/testing would be helpful from my end on this followup issue. (assuming you have time/motivation to work on it further)