UI misbehaves when deploying new version of the App

[2opremio]

To test the 0.12 release in ECS, I started by deploying the current stable version (0.11.1), opening the UI to see everything was working properly and then deployed the 0.12 candidate without closing the browser.

This is the UI talking to version 0.1.1

This is what happened after deploying the 0.12 candidate without manually reloading the UI. The version tag in the UI updated but the detail panel doesn't work (there's an infinite spinning wheel) because the detail panel data structures changed in 0.12 but the the javascript files were not reloaded (i.e. the browser still had the ones from 0.11.1):

This is understandable to certain extent, but the UI didn't work after reloading the page either.

I needed to do an "Empty Cache and Hard-reload" in Chrome to make it work, which is strange because I see that all the javascript files (at least in 0.12) are served with cache-control:no-cache

An easy solution would be forcing a UI-reload when a version change is detected but I don't know if that would solve the caching problem.

[davkal]

Yeah, that is an important issue. Let's do bundle fingerprinting and display an info message when a change in version in /api is detected.

[pidster]

Would it be preferable to consider this to be part of an API versioning & compatibility problem?

[2opremio]

This is still a problem when upgrading the app, even after #1354

In the example below, the app is using Scope 0.15, which introduced the search-bar. However, the search bar is missing ...

... and it only started appearing after wiping the cache and hard reload.

This is particularly important for the service, during the upgrade of the user apps from 0.13.1 to 0.15 the UI completely stopped working.

[davkal]

Stand-alone scope is not affected anymore.