Service Worker did not update

🐛 bug report

I don't quite know where to post this; there was no response to the tweet.

Description of the problem

I've only just been able to use the new codesandbox client because, as it turned out, my service worker did not update correctly. Other parts of the code don't check for your current version and broke in magical ways. (e.g. code would stop reloading, or reload after a few minutes without change, or random console errors).

This was the only error I could capture -- note that the site looked like months ago: no tabs on the "new sandbox" page.

This is before I did anything. As you can see, the old service worker is still here; I don't understand why the date here says UNIX 0.

This is after I forced clearing the cache. The new site loaded almost instantly.

How has this issue affected you? What are you trying to accomplish?

I was trying to add an mdx-deck sandbox and couldn't find it.

The bug for me is resolved by clearing the cache, but perhaps you want to look into this for a next update.

Original tweet

https://twitter.com/SleeplessByte/status/1125794586096480258

Hi @codesandbox ; something went wrong with your massive update.

I had to manually clear everything in order to get the new site. All my sandboxes were behaving weirdly and when I saw amazing videos of new features by @NikkitaFTW it prompted me to figure this out.

Your Environment

No source file or test is named in the report. Start by reproducing the stale service-worker behavior described in Chrome and inspect the service-worker state before and after an update. Done means a new release loads without manually clearing the cache and the reported stale-site behavior is no longer observed.