search

tomer8007 / whatsapp-web-incognito

A Chrome extension that disables read receipts and presence updates on WhatsApp Web
MIT License
312 stars 74 forks source link

Extension breaks after WhatsApp version 2.3000 #159

Closed tjodiro closed 3 months ago

tjodiro commented 3 months ago

This version is not working and is not loading any update?

tomer8007 commented 3 months ago

Thanks for opening an issue. What's the WhatsApp Web version you're using? The extension works for me in 2.2411.2.

inalam commented 3 months ago

@tjodiro do you use WA Web Plus by Elbruz Technologies? try disable it, mine works after that

anyway i do need blur chat feature that WA Web Plus offers, if tomer had time to implement it. much appreciate

tjodiro commented 3 months ago

nothing seems to work

On Tue, Mar 19, 2024 at 6:17 AM inalam @.***> wrote:

@tjodiro https://github.com/tjodiro do you use WA Web Plus by Elbruz Technologies? try disable it, mine works after that

— Reply to this email directly, view it on GitHub https://github.com/tomer8007/whatsapp-web-incognito/issues/159#issuecomment-2006690471, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHCINWVIUGEOZBVCHOC4QXTYZAGCJAVCNFSM6AAAAABE3W4SS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBWGY4TANBXGE . You are receiving this because you were mentioned.Message ID: @.***>

GHMFL0369 commented 3 months ago

the whats app version is Version 2.3000.1012148573

GHMFL0369 commented 3 months ago

Screenshot 2024-03-19 071234

tomer8007 commented 3 months ago

@GHMFL0369 Looks like the message is self-explanatory.

GHMFL0369 commented 3 months ago

Screenshot 2024-03-19 195652

inalam commented 3 months ago

@GHMFL0369 have you try enabling the beta? using non beta makes my version in 2.3000 and beta could go to 2.2412.1

tomer8007 commented 3 months ago

@inalam Does anybody have a tip on how to enter 2.3000? I'm having some trouble moving to this version from 2.2412.1.

tomonetml commented 3 months ago

@tomer8007 probably enabling betas in settings, help. then clear cache

tomer8007 commented 3 months ago

@tomonetml Already tried that, and also trying from another OS, browser, and re-logging in didn't help moving out of 2.2412.1.

inalam commented 3 months ago

@inalam Does anybody have a tip on how to enter 2.3000? I'm having some trouble moving to this version from 2.2412.1.

i just uncheck the beta image

version with beta image

and always empty cache and hard refresh between change image

it's weird the fact that beta has lower version than official(?)

tomer8007 commented 3 months ago

and always empty cache and hard refresh between change

Yep I always do this

it's weird the fact that beta has lower version than official(?)

Absolutely

For me both options still leave me in 2.2412.1. My phone also runs version 2.24.X. I think that 2.3000 is in some kind of limited edition, perhaps only for some users.

IsaacHatton commented 3 months ago

My main whatsapp account is broken in stable, I tried it in beta also. With WAdebugMode enabled: image

I presume the first error is due to some UI based change, but I don't know about the second.

IsaacHatton commented 3 months ago

For the UI change, here's what the new DOM looks like for where the buttons are image

tomer8007 commented 3 months ago

Can anyone share thoughts about how to enter the new version? Do you know others that have 2.2411.2 and can tell the difference?

IsaacHatton commented 3 months ago

I have found that if you are in stable 2.24... and you switch to beta and reload it upgraded me most times.

I by using various browser profiles have managed to get it to pick me either versions, I think it's based on an identifer in the browser rather than the account as to whether you get selected for the A/B test.

tomer8007 commented 3 months ago

I'm having some trouble moving to this version from 2.2412.1.

image Adding Cookie: wa_beta_version=production/1710826334/2.2412.1; wa_build=c; to the headers did the trick.

I by using various browser profiles have managed to get it to pick me either versions

What OS and browser did you use?

IsaacHatton commented 3 months ago

I by using various browser profiles have managed to get it to pick me either versions

What OS and browser did you use?

Win 11: both Edge and Chrome

tomer8007 commented 3 months ago

@IsaacHatton So how did you make it pick 2.2412.1 vs 2.3000?

IsaacHatton commented 3 months ago

@IsaacHatton So how did you make it pick 2.2412.1 vs 2.3000?

Just keeping logging in and out in different browsers, I did not have a methodology really.

m4heshd commented 3 months ago

@tomer8007 It's a staged rollout. You might need to wait a couple of days.

Also, always use the browser's Guest profile/mode to log in. Even incognito can sometimes affect how the headers are sent back to their endpoint to decide if you're a viable candidate for the update.

tomer8007 commented 3 months ago

You might need to wait a couple of days.

As I said I managed to make WhatsApp update me to the new version by adding wa_build=c; to the cookies. Looks like this is really new, even newer than the newest version available for beta testers in Android and iOS. It appears they're now using React Native for the web.

UPDATE: @IsaacHatton I have released version 2.1.5 of the extension which adds support for WhatsApp Web 2.3000.

IsaacHatton commented 3 months ago

You might need to wait a couple of days.

As I said I managed to make WhatsApp update me to the new version by adding wa_build=c; to the cookies. Looks like this is really new, even newer than the newest version available for beta testers in Android and iOS. It appears they're now using React Native for the web.

UPDATE: @IsaacHatton I have released version 2.1.5 of the extension which adds support for WhatsApp Web 2.3000.

Thanks for releasing that, it works great for me, has it updated on the chrome webstore yet or does Google require manual approval for updates (I only have experience with the Edge extension store)?

tomer8007 commented 3 months ago

has it updated on the chrome webstore yet

Yes, version 2.1.5 is live on the store now.

IsaacHatton commented 3 months ago

Thanks.

Just as a thought, if you could pick which version you got served, as a long term strategy could there be a system implemented wherein if the extension fails to load and it detects there's a newer version, it can add the header to downgrade to the old one?

tomer8007 commented 3 months ago

Currently version 2.1.5 is backward-compatible with both 2.3000 and 2.24.X (tested on both). In case WhatsApp releases a new version that breaks stuff, you normally see the popup that @GHMFL0369 posted earlier in this thread.

tomer8007 commented 3 months ago

As for downgrading WhatsApp versions, we need to be sure what wa_build actually means.

IsaacHatton commented 3 months ago

Oh ok, that makes sense. I misread this:

Adding Cookie: wa_beta_version=production/1710826334/2.2412.1; wa_build=c; to the headers did the trick.

as when you put wa_beta_version you could select the version from there.

I presume any kind of system to automatically send error logs when that popup appears wouldn't be allowed under app store rules, as the Privacy Policy says so https://github.com/tomer8007/whatsapp-web-incognito/wiki/Chrome-Extension-Privacy-Policy ?

tomer8007 commented 3 months ago

as when you put wa_beta_version you could select the version from there.

Yeah, I'm still not certain about exactly what is the purpose of this cookie.

any kind of system to automatically send error logs

Yes, I don't like this privacy-wise, it requires me to setup and maintain a back-end system, and I think most of the time users will already complain and I will also note that myself.

tomer8007 commented 3 months ago

Closing this because it's fixed now