Open pheijmans-zz opened 5 years ago
Same problem here!
Same issue on a fully updated Fedora box.
+1
Thanks, there are some cases where the UserAgent is slightly malformed which throws up this problem. There's a fix coming out for this very shortly
Thanks everyone for reporting. It looks like the root cause is that the UserAgent is slightly malformed in the ServiceWorker which causes WhatsApp to incorrectly report that the browser is out of date. This doesn't seem to happen on all machines but after a certain sequence of events.
We've pushed a fix out in version 4.10.1 which addresses this so it shouldn't happen again.
After updating, depending on how the UserAgent detection failed, you may need to clear browsing data for this account or re-add it. Either option should clear the message...
Clear browsing data
Clear all browsing data
Re-add the account
Delete Account
Awesome, works like a charm :) Thanks for the fast update!
I'm adding to this. I stupidly decided to delete the WhatsApp service and now the QR code does not work when I try to scan from the phone. Works fine when using Chrome desktop.
I'm on 4.10.1.
EDIT: I figured it out. I had Dark Reader on. Dark Reader stops the QR code from working ...
@zeusontwowheels thanks for the info about the Dark Reader :)
@zeusontwowheels …and thanks for the tip to Dark Reader.
Wavebox Version: 4.10.0 Operating System & Version: windows 10 Account type (if applicable): WhatsApp Web
Expected & actual behavior WhatsApp worked in the last beta, but is now broken in 4.10.0 WhatsApp works with Google Chrome 36+ To use WhatsApp, update to CHrome or use Mozilla Firefox, Safari, Microsoft Edge or Opera. [download goodo chrome button]
Steps to reproduce Simply try to use a WhatsApp account. Reproducible with account, or by removing and creating new account.
Is the bug persistent or intermittent? Persistent
Screenshots Attached