Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

View Once Messages no longer working #543

Open
emp3r0r7 opened this issue Feb 4, 2025 · 2 comments
Open

View Once Messages no longer working #543

emp3r0r7 opened this issue Feb 4, 2025 · 2 comments
Labels
waiting triage A maintainer acknowledged the issue, further discussion is needed

Comments

@emp3r0r7
Copy link

emp3r0r7 commented Feb 4, 2025

Hello, it seems that recently Cobalt is no longer able to decode or trigger listeners for view-once messages. After analyzing the responses from WhatsApp for these types of messages, it appears that the 'content' field in inbound view-once messages is no longer populated or is completely missing, which means the binary is not present.

Running Cobalt 0.0.6

This message is received upon getting a viewonce message :

Node[description=message, attributes={verified_level=unknown, t=173, recipient=XXXXXXXXXXXXX@s.whatsapp.net, verified_name=7320, from=XXXXXX@s.whatsapp.net, id=717XXXX, type=media, notify=Device...}, content=[Node[description=unavailable, attributes={type=view_once}]]]

My guess is that Whatsapp no longer attaches the media to the view once message in whatsapp web.

If anyone can check this problem aswell and confirm would be nice. Thank you.

@Auties00
Copy link
Owner

Auties00 commented Feb 4, 2025

Can you test 0.0.8?

@Auties00 Auties00 added the waiting triage A maintainer acknowledged the issue, further discussion is needed label Feb 4, 2025
@emp3r0r7
Copy link
Author

emp3r0r7 commented Feb 5, 2025

Can you test 0.0.8?

@Auties00

I'm using the web pairing method.

I have tested version 0.0.8 and encountered some issues. Specifically, I used commit 008f5a0 because the latest commit (d66dfa1) resulted in OTP pairing failures due to request timeouts ("Cannot login: no response from Whatsapp"), preventing me from creating new sessions for testing. Additionally, with the latest commit (d66dfa1) , while QR code pairing generates the base64 or QR code correctly in the console, I experience a socket failure during login as soon as I attempt to connect using this method.

Using commit 008f5a0, I successfully paired a device using the OTP code and tested view-once messages. However, I noticed that these messages are not being captured in 0.0.8 too.
Again , i assume Whatsapp doesn't include view-only messages in the payload within whatsapp web anymore , but only through the master device.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting triage A maintainer acknowledged the issue, further discussion is needed
Projects
None yet
Development

No branches or pull requests

2 participants