Sometimes, roughly every 2-3 months, WhatsApp Web (web.whatsapp.com), that I access through Chrome or Chromium, displays a green banner at the top of the left column:

Update available - Click to update Whatsapp

"Update available. Click to update WhatsApp"

Clicking triggers a page refresh, then WhatsApp operates normally (it doesn't require a new pairing with the device). Actually, it is operative while the banner is displayed too, i.e. before accepting the update, too.

This usually appears at the start of a session (right when I visit the page), but it has also happened mid-session.

I'm confused by this request: the page has already the permission to set (and, I believe, update) its cookies, and it doesn't run any additional software on my computer. I wouldn't think it needs to do anything client side. So what is it updating and why would it need my click?

Edit: some recent update events: 16 October 2018, 5 April 2019, 24 September 2019, 11 October 2019.

  • Old question but still relevant and unanswered? I would love to understand this as well. I assume it needs reloading because it wants to update scripts and needs to refresh, but doesn't want to refresh by itself without user consent? – Gabriel Sprenger Sep 23 '19 at 14:19
  • i haven't seen it happening in a while now, so I don't know if it's still relevant. As per your conjecture: I think I've seen the message appearing just at the start of a session, so when it could have just loaded with the new scripts – Nicola Sap Sep 23 '19 at 21:54
  • 2
    Posting as a comment since I don’t have sufficient rep for an answer. Part 1/2 The WhatsApp web app is fully cached in your browser & uses a service worker to manage itself. Advantages of caching an app include and are not limited to reduced payload sizes & offline capabilities. So every refresh only downloads a small payload including the service worker since the application is already cached! Pretty neat huh? – Awad Maharoof Aug 28 '20 at 2:22
  • 2
    Part 2/2 A service worker can detect when the app is outdated and can trigger a message like the one you've mentioned. The reason not to automatically refresh is a UX decision I believe, because it would suck if the page decided to refresh itself while you were typing a message. – Awad Maharoof Aug 28 '20 at 2:22
  • 1
    Thanks! That's a useful answer! How come you can't post an answer? The webapps.stackexchange.com/help/privileges/create-posts priviledge comes at 1 rep, much earlier than the webapps.stackexchange.com/help/privileges/comment – Nicola Sap Aug 28 '20 at 9:36

WhatsApp uses a service worker that cache some scripts, but the browser see the necessary scripts update only loaded the the page, because, he search for code change in the service worker. For this, WhatsApp hint you about it. It could also reload the page after the service worker update, but it also want that the user view the update and decides when it's opportune to reload the page.

Not the answer you're looking for? Browse other questions tagged or ask your own question.