Fixed
- After an upgrade, the interface could fail to load at all and show a red
JS Errorinstead. The browser was mixing files from two different releases: the new interface was loading, but some of the smaller files it is built from were still coming from an old copy held in the browser's cache. Those files are loaded as one unit, so one mismatch stops the whole interface rather than breaking a single panel. mikr now always fetches those files from the server after an upgrade instead of accepting whatever the browser has kept, and it asks browsers and any proxy in front of the installation to check with the server rather than reuse an old copy. If you are seeing this now, the fix reaches you as soon as the page loads once — see below. - An interface stuck in that state could not repair itself. The part of mikr that installs the update is inside the same unit that had failed to load, so the installation could never replace the broken copy, and no later release would have helped either. Clearing the browser's site data by hand was the only way out, which is not a reasonable thing to ask of someone holding a phone. mikr now detects that the interface never started, clears its own caches and reloads, once. If that does not resolve it, the error screen now carries a Clear cache and reload button instead of being a dead end. This only ever runs when nothing has loaded — an error while you are working will never reload the page out from under you.