Bug 280582 - Unable to login to WhatsApp after latest update
Summary: Unable to login to WhatsApp after latest update
Status: RESOLVED DUPLICATE of bug 275890
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: PC Linux
: P2 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-29 07:01 PDT by kbodragin
Modified: 2024-09-29 14:46 PDT (History)
2 users (show)

See Also:

Attachments
Screenshot of the login window - the QR doesn't load (38.10 KB, image/png)
2024-09-29 07:01 PDT, kbodragin 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kbodragin 2024-09-29 07:01:42 PDT 
Created attachment 472727 [details]
Screenshot of the login window - the QR doesn't load

After latest update, WhatsApp web doesn't load the QR code for logging in. I can't use the login with phone number feature, either.


WebKitGTK 2.46.0
GStreamer 1.24.7
GTK 4.16.1
Libadwaita 1.6.0
Distributor: GNOME
Comment 1 Adrian Perez 2024-09-29 12:37:37 PDT 
Hi! Thanks for the bug report. We have a fix for this, see bug #275890
The upcoming 2.46.1 release will include the patch in the coming days.

*** This bug has been marked as a duplicate of bug 275890 ***
Comment 2 kbodragin 2024-09-29 13:39:02 PDT 
(In reply to Adrian Perez from comment #1)
> Hi! Thanks for the bug report. We have a fix for this, see bug #275890
> The upcoming 2.46.1 release will include the patch in the coming days.
> 
> *** This bug has been marked as a duplicate of bug 275890 ***

Thanks! I must've missed the old report.
Comment 3 Adrian Perez 2024-09-29 14:46:31 PDT 
(In reply to kbodragin from comment #2)
> (In reply to Adrian Perez from comment #1)
> > Hi! Thanks for the bug report. We have a fix for this, see bug #275890
> > The upcoming 2.46.1 release will include the patch in the coming days.
> > 
> > *** This bug has been marked as a duplicate of bug 275890 ***
> 
> Thanks! I must've missed the old report.

No problem at all =)