0

I am working on a site. I got this from a client to be redesigned. The old design was made by some other agency. Once I was done, and changed old DNS records to the new server and went live with the new design, everything worked OK. Except, for old users of the site.

All old users couldn't see the new design. I did everything I could to force the browser to forget cache by using HTTP Headers, .httaccess etc. Nothing worked.

I later found that the old design was built on PWA technology. Progress Web Apps which can be installed as an app on the device. And this app used something called worker cache to store static files in the Cache Storage and Application cache.

Now for some reason, old users' browsers are not willing to forget that cache at all. Looks like the browser isn't even hitting my new server / DNS settings for the new design. It just takes the content from the worker/application cache and displays the old site.

I can't ask users to clear their cookies or cache, or uninstall the app individually. How can I get rid of this cache from old users' browsers so that the new design is working on those devices too?

Any ideas?

arxoft
  • 1,385
  • 3
  • 17
  • 34
  • 1
    "Looks like the browser isn't even hitting my new server" - Have you confirmed this in your server logs? In that case there's nothing you really can do without user intervention. The same with any persistent client-side caching. – MrWhite Nov 04 '21 at 11:00
  • @MrWhite Yes, that's confirmed. The browser isn't even hitting my server. There must be some way how PWA's update to new versions... – arxoft Nov 04 '21 at 12:57
  • 1
    https://stackoverflow.com/questions/33986976/how-can-i-remove-a-buggy-service-worker-or-implement-a-kill-switch/38980776 has details about recovering from this scenario. – Jeff Posnick Nov 04 '21 at 12:58

0 Answers0