For some reason, in Chrome (latest version), Urza Gatherer kept loading as v9.9.7 (or whatever the latest 9.9.X version was).
I tried:
1) Refreshing the page.
2) Opened dev-tools (with "Disable cache" on), and hard-refreshed the page. This temporarily solved it, but the issue returns as soon as I close the dev-tools and refresh.
3) Cleared all cached images/files in my browser, then redid steps 1-2.
4) Updated Chrome to the latest version, and completely restarted Chrome.
5) Cleared all local-storage and cookies of the site, then redid steps 1-2.
6) Manually went into the dev-tools -> application -> service workers panel, and tried updating the worker; no improvement.
7) Tried enabling the "Bypass for network" option. This worked while dev-tools was open with that option enabled, but the site reverted to 9.9.X when I closed dev-tools and refresh.
8) Tried "Updating" the service-worker, then "Unregistering" it, with "Disable cache" on, then pressed "Empty cache and hard refresh" on the refresh button. Again, worked temporarily, but the site reverted to 9.9.X as soon as I closed dev-tools and refreshed.
Having a background in web-development, I was getting quite annoyed with how the service worker somehow -- apparently -- kept retrieving an old version of the site and trying to run it. I eventually decided there is probably a bug deep somewhere in either Urza Gatherer or Chrome (I suspect it's a bug in Chrome, although maybe there's some developer-side workaround that could be implemented).
In the end, I did finally find a solution:
1) I installed the "Block Service Workers" extension: https://chrome.google.com/webstore/detail/block-service-workers/ceokjgeibfjfcboemhdpkdalankbmnej
2) I did an "Empty cache and hard refresh" of Urza (just to be sure). The extension popped up a message asking if it should allow the service-worker to be installed/used.
3) I said "No"; and yay, v10.0.X showed up as desired.
4) I did some more fiddling around to confirm the issue was actually fixed, including clearing the extension's blocking, trying more hard-refreshes, etc.
5) After that period of fiddling, I did some regular refreshes with the dev-tools closed, and *finally* the issue seems to be resolved. (the v9.0.X has not shown up again since then, thank goodness)
Anyway, since I didn't see any results for this issue during a search for it on these forums, my guess is that the problem is either rare, or something most people don't notice.
It's probably not even worth your time to investigate it. However, because of how annoying/hard-to-fix the issue was, I figured I would mention it on these forums so people in the future can find this information through search, if/when needed.
Okay, I think I finally fixed the core issue. (knocking on wood) What I did (after disabling the workaround extension for blocking/gating all service-workers): 1) Closed all UrzaGatherer tabs. 2) Turned off my internet. 3) Opened UrzaGatherer, went to Settings, then pressed "Clear local cache" in the database section. 4) Turned internet back on. 5) Refreshed the page. (and again, and again, and in new tab, and with dev-tools open and closed, and with hard-refresh, etc. to make sure the fix persisted)
So the key seems to be the "Clear local cache" button in the "Database" section at the bottom of settings. It's odd that that did it though, since as mentioned I already tried clearing all cache for UrzaGatherer through the dev-tools; but maybe UrzaGatherer has some kind of "cache" that is not seen by the dev-tools cache-clearing tool.
If the app's "Clear local cache" button is not supposed to have anything to do with the service-worker code (ie. app version), then my suspicion is that maybe there was something about what the app was caching that was making the app's state "invalid" or "over a quota" or something, causing the attempt to update the cached service-worker code (to the newer versions) to consistently fail. And so by pressing "Clear local cache", it restores the app's state to something that wasn't invalid/over-quota, freeing that up.
Anyway, the above is just a guess; the fix above worked for me (and without needing that service-worker-blocker extension anymore), so I am content not knowing the full details.
Update 2: I've made some additional observations: 1) When using the service-worker-blocker extension, it appears that the "OneDrive" sync provider does not work. (the console just says "Working offline" whenever I try to connect to it) 2) I then tried to reset the blocker extension, and this time clicked "Yes" when asked whether to allow the service-worker. Oddly, this seems to fix the service-worker versioning issue, even with dev-tools closed and refreshing normally. (so long as the extension is kept active)
3) With the service-worker now allowed (after passing through the extension gatekeeper), the "OneDrive" sync provider somehow was still failing! (with the same "Working offline" message)
4) However, when I switched to the "DropBox" sync provider, it was able to connect -- and I successfully pushed and pulled from my cloud storage.
5) So there is one path to fix the issue I've been hitting, when in Chrome: install the service-worker-blocker extension, then reload urza and say "yes" for allowing the service-worker, then just always use DropBox as your sync provider going forward rather than OneDrive.
😑
I spoke too soon. Somehow the "reversion to 9.9.5" is back, now that I've disabled the extension.
So the extension didn't really "fix" the issue long-term -- it apparently just blocked the issue from showing up, while active.
That said, at least there is a workaround. (keeping that extension enabled long-term, to always block Urza's service-worker from ever being used)
(Another reason I think Chrome is at least partly to blame is that this issue is not happening in Firefox for me -- at least not currently.)