This might be useful reading: http://stackoverflow.com/questions/33986976/how-can-i-remove-a-buggy-service-worker-or-implement-a-kill-switch which also links to this information http://stackoverflow.com/questions/38843970/service-worker-javascript-update-frequency-every-24-hours/38854905#38854905

The long and the short of it is that we can replace the service-worker.js on our server at any time and browser will update to this new file at the point the user navigates to our site with the following caching restriction: the old service-worker.js file will be cached for either the length of time specified in the caching headers or 24 hours, whichever is shorter.

So the only thing we need to do right now is:

a) set our caching period to a length of time <24 hours that we deem as appropriate. I suggest 60 mins.
b) create a noop-service-worker.js file that we can apply quickly in an emergency that effectively disables the service worker.

a) The default cache time for Firebase files is 3600 sec, so the worker-basic.min.js is already set to expire every hour.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}