You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :
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.
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.
The text was updated successfully, but these errors were encountered: