1756974 - WhatsApp Web bug with login through QR Code on Firefox 97.0.1 (64-bit)

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Graphics: WebRender

Product: Firefox → Core

Timothy Nikkel (:tnikkel)

Updated

•

3 years ago

Component: Graphics: WebRender → DOM: Navigation

Mirko Brodesser (:mbrodesser) -- not reading bugmails currently

Comment 3

•

3 years ago

Morpheus: with "strict mode" ETP strict mode is meant?

If so, could you be so kind to try to reproduce the issue in ETP standard mode and report the result here?

Flags: needinfo?(gheorhios)

Alin Ilea, Desktop Test Engineering

Comment 4

•

3 years ago

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0

Hi,

I have tested your issue in Release 97, Beta 98, and the latest Nightly build 99.0a1 (2022-03-02) but could not reproduce it using Windows 10. I can successfully login into whatsupp web with strict mode enabled as well.
If the issue is still reproducible on your end, can you please retest this using the latest Nightly build (https://nightly.mozilla.org/) using a new clean Firefox profile (https://goo.gl/AWo6h8) to eliminate the potential causes?

Thanks for the report.

Morpheus Ziplon

Reporter

Comment 5

•

3 years ago

Hello there,

I just found these error happens on the following situations:

Firefox 97.0.1 (64-bit)
If user disable "remember history"
All user modes

Thanks you for helping.

Flags: needinfo?(gheorhios)

Mirko Brodesser (:mbrodesser) -- not reading bugmails currently

Comment 6

•

3 years ago

@Alin: can you please retest the issue with Settings -> Privacy & Security -> History -> "Never remember history" selected. That seems to be the reporter's scenario.

@Morpheus: if your Firefox uses any plugins, that'd be helpful to know.

Flags: needinfo?(alin.ilea)

Alin Ilea, Desktop Test Engineering

Comment 7

•

3 years ago

•

Edited

(In reply to Mirko Brodesser (:mbrodesser) from comment #6)

@Alin: can you please retest the issue with Settings -> Privacy & Security -> History -> "Never remember history" selected. That seems to be the reporter's scenario.

Just tried using the comment 5 scenarios (Fx 97.0.1 64bit, History -> "Never remember history") but I get the same results, works ok on my end, I am able to log into WhatsApp web in a few seconds using the QR code without any issues on Windows 10. Also verified using both standard and strict Enhanced Tracking Protection options.

@Morpheus: if your Firefox uses any plugins, that'd be helpful to know.

Flags: needinfo?(alin.ilea) → needinfo?(gheorhios)

Morpheus Ziplon

Reporter

Comment 8

•

3 years ago

(In reply to Mirko Brodesser (:mbrodesser) from comment #6)

@Alin: can you please retest the issue with Settings -> Privacy & Security -> History -> "Never remember history" selected. That seems to be the reporter's scenario.

@Morpheus: if your Firefox uses any plugins, that'd be helpful to know.

@mbrodesser only the following:

OpenH264 Video Codec provided by Cisco Systems, Inc.
Widevine Content Decryption Module provided by Google Inc.

Thank you

Flags: needinfo?(gheorhios)

Morpheus Ziplon

Reporter

Comment 9

•

3 years ago

After new Firefox installation still impossible to login to Whats App Web under these conditions:

Strict mode
Never remember history

I believe the login is made in "two steps" now each means the App reads qr code twice.

Thank you

Vincenzo

Comment 10

•

3 years ago

The problem of the page refresh non-stop loop persists also in Firefox 97.0.2.
In Edge, WhatsApp Web works regularly.

BugBot [:suhaib / :marco/ :calixte]

Comment 11

•

3 years ago

The severity field is not set for this bug.
:annevk, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(annevk)

Hsin-Yi Tsai (she/her) [:hsinyi]

Comment 12

•

3 years ago

I managed to reproduce this on Fx 98, Win11, if I joined "What's app "multi-device beta."
Morpheus or Vincenzo, did you join "multi-device beta" when you saw the problem? Thank you.

Flags: needinfo?(viscas2001)

Flags: needinfo?(gheorhios)

Flags: needinfo?(annevk)

Hsin-Yi Tsai (she/her) [:hsinyi]

Comment 13

•

3 years ago

I got these errors in console on Fx 98:

Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. bootstrap_qr.79aba964bea38dbcc501.js:12:186640

I couldn't reproduce this issue on nightly. Do we have behavior differences in Nightly and Release?

Moving to Networking: WebSockets component due to the error message.

Component: DOM: Navigation → Networking: WebSockets

Vincenzo

Updated

•

3 years ago

Flags: needinfo?(viscas2001)

Vincenzo

Comment 14

•

3 years ago

Hi everyone and thanks for your interest in my problem.
I am not sure, but I believe that, unintentionally, I joined "What's app "multi-device beta."
I don't know how to get out of the "multi-device beta".
I don't have any problems on Microsoft Edge, though.

Regards
Vincenzo

Morpheus Ziplon

Reporter

Comment 15

•

3 years ago

Microsoft Windows 10 Home 21H1 19043.1586

Firefox 97.0.1 - 98.0.1 (64-bit)

Plugins

OpenH264 Video Codec provided by Cisco Systems, Inc.
Widevine Content Decryption Module provided by Google Inc.

WhatsApp Web login through QR code page refresh non-stop loop

If user disable "remember history"
All user modes

I created a new firefox profile and did not join whatsapp "multi-device beta".

Thank you

Flags: needinfo?(gheorhios)

Kershaw Chang [:kershaw]

Comment 16

•

3 years ago

Could you try to record a http log?
Please also add nsWebSocket:5 to MOZ_LOG.
Thanks.

Flags: needinfo?(gheorhios)

rashid_usm

Comment 17

•

3 years ago

I have the same issues with Firefox 98.0 on Fedora 34. I did not join the Whatsapp Beta but today Whatsapp asked me to update Whatsapp Web (no mention of Beta anymore). And after I did that, whenever I open https://web.whatsapp.com and try to scan the QR code with my phone, the code will immediately disappear and a spinning wait symbol appears in place of the QR code. If my mouse is in the window I can also see that in the lower left corner the Firefox link preview "web.whatsapp.com" is flickering very fast. After a minute or so, the Whatsapp page completely reloads with a red banner at the top saying "A database error occurred on your browser. Please restart your computer and relink your device."

The problem only appears when I tell Firefox not to remember history.

I recorded an http log with export MOZ_LOG=timestamp,rotate:200,nsHttp:5,cache2:5,nsSocketTransport:5,nsHostResolver:5,cookie:5,nsWebSocket:5. Unfortunately, it is too large to append as an attachment to this ticket. So I have uploaded it to mega.nz:
https://mega.nz/file/BUMggZBJ#105BrpKq8jwsJapTAey-3kpfyvYYpfjhgUp2JTC56wE

Timothy Nikkel (:tnikkel)

Updated

•

3 years ago

Flags: needinfo?(kershaw)

Rainer Meier

Comment 18

•

3 years ago

I am having the same problem. Although I can reproduce it only if I am opening a private window on Firefox 99. In non-provivate window it is working fine but login on https://web.whatsapp.com/ is impossible in private window.
So it might be related to history or strict mode which might be handled differently in private mode.

Interestingly I am using Whatsapp 2.22.7.74 on two phones. One of them allowing me to join and leave multi-device beta. The other one (the one I am trying to connect to WA web) isn't offering this option.

So perhaps someone can confirm this issue in private mode.

Kershaw Chang [:kershaw]

Comment 19

•

3 years ago

Thanks for the log.
I've seen that the websocket connection is closed by the server. Looks like Firefox did nothing wrong.

2022-04-05 19:51:10.936215 UTC - [Parent 334689: Socket Thread]: D/nsWebSocket WebSocketChannel:: close received
2022-04-05 19:51:10.936218 UTC - [Parent 334689: Socket Thread]: D/nsWebSocket WebSocketChannel:: close recvd code 1000

Could you go to about:config and set network.http.spdy.websockets to false and see if this helps?
Thanks.

Flags: needinfo?(kershaw) → needinfo?(rashid_usm)

Rainer Meier

Comment 20

•

3 years ago

For me disabling network.http.spdy.websockets did not do any change for Whatsapp Web in private window.
Firefox seems to loop/redirect continously (also losing focus on URL bar, being unable to overwrite the URL as constantly the URL is being refreshed).

Sometimes after reloading the page several times I am getting the error "A database error occurred on your browser. Please restart your computer and relink your device." which makes me believe it might be related also to local storage access. I did also face similar issues after getting an incomplete/inconsistent storage database in "<profile-folder>\storage" folder. This folder is by the way still stored in the completely wrong directory on Windows (within the roaming rather than the local path of the user profile) causing various issues with roaming user profiles including also incomplete sync and Firefox failing to work properly.
Sometimes the only way to solve it is to remove the "storage" folder entirely, then going to firefox settings (about:preferences#privacy) and deleting all data in "Manage Data..." section. Then restarting Firefox.
Firefox seems to have huge issues dealing with broken/inconsistent data in this folder and unfortunately isn't handling it properly either. So this is a common and known issue since years.
However in this case here I can reproduce the issue always (also with a fresh profile) in a private window.

Kershaw Chang [:kershaw]

Comment 21

•

3 years ago

Thanks. I can reproduce this locally in a private window.
I also noticed lots of error message below. When tested this in a normal window, the following error messages didn't show.

[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'ToResult(Open()) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15739
[Parent 79805, Main Thread] WARNING: QM_TRY failure (ERROR): 'CheckPermission(contentParent) failed with resultCode 0x80660006, resultName NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR', file dom/indexedDB/ActorsParent.cpp:15220

I think this bug is more related to Storage component.

Component: Networking: WebSockets → Storage: IndexedDB

Vincenzo

Comment 22

•

3 years ago

Hello to all

I was able to solve the problem with Firefox 99.0.
In privacy and security by removing the anonymous browsing and putting a flag in “delete cronology only when leaving Firefox”, now Whatsapp Web works well.

Best regards
Vincenzo

Rainer Meier

Comment 23

•

3 years ago

Thanks @Vincenzo, it was already suspected to be related to the Storage component. Storage is handled differently in private browsing sessions as well as if history is disabled. So the problem remeins in private browsing sessions as well as it does for people having history disabled. None of those should actually break any web applications but should potentially just make sure this data is not stored permanently.

Morpheus Ziplon

Reporter

Comment 24

•

3 years ago

(In reply to Vincenzo from comment #22)

Hello to all

I was able to solve the problem with Firefox 99.0.
In privacy and security by removing the anonymous browsing and putting a flag in “delete cronology only when leaving Firefox”, now Whatsapp Web works well.

Best regards
Vincenzo

Hello there,

If that work for you, seems a work around not a solution.

Thanks you for helping.
Morpheus

Flags: needinfo?(gheorhios)

Jens Stutte [:jstutte]

Comment 25

•

3 years ago

So for the IndexedDB part: Bug 1639542 tracks the (currently missing) support for IndexedDB in private browsing mode.
Same goes for Service Workers (I believe, whatsapp needs those, too): bug 1320796.

Depends on: idb-private-browsing

Updated

•

3 years ago

Severity: -- → S3

Priority: -- → P3

Morpheus Ziplon

Reporter

Updated

•

3 years ago

OS: Unspecified → Windows 10

Hardware: Unspecified → Desktop

Morpheus Ziplon

Reporter

Updated

•

3 years ago

Status: UNCONFIRMED → RESOLVED

Closed: 3 years ago

Resolution: --- → WORKSFORME