stops receiving messages when the id starts with 66

[Valdenirmezadri]

Good afternoon, when a message with the id starting with 66 is received, I stop receiving messages. just reading it again the qrcode works again

Oct 03 2024 11:20:20 client.go:708 ▶ DEBU <offline_preview appdata="0" call="0" count="12" message="9" notifi
cation="0" receipt="2"/>
Oct 03 2024 11:20:20 client.go:708 ▶ DEBU <thread_metadata></thread_metadata>
Oct 03 2024 11:20:20 client.go:708 ▶ DEBU

[leonetosoft]

The same happens on JS library.
It is drive me crazy.
Lets take a look in the message ID and issue ID

666

😈

[purpshell]

The same happens on JS library. It is drive me crazy. Lets take a look in the message ID and issue ID

666

😈

hahahaa

This is happening on official clients as well. I am fully investigating this on Baileys as well on whatsmeow after lots of reports from my clients on both libraries. We believe its rooted in the libsignal library.

The problem is even bigger than this, there are accidental issues/crashes like these ones but there are people also caught selling these types of messages to deliberately crash Android/iOS and to completely disable Web/Desktop/the libraries.

The way this destroys whatsmeow and Baileys is by forcing the app to quit (due to a failure in decryption), thus never acking the message, and after this happens like 10 times, the socket is unrecoverable (the socket considers that you are not receiving any messages anymore, so it no longer sends you any new messages)

[leonetosoft]

@purpshell than you for yout assistance.
Here the socket is unable to receive messages but I can send messages normally.
I made a deep investigation and there is a business using this type of ID but isn't on purpose. Is a chatbot as well.
I think they are using ID coming from MongoDB databases.

[purpshell]

@purpshell than you for yout assistance. Here the socket is unable to receive messages but I can send messages normally. I made a deep investigation and there is a business using this type of ID but isn't on purpose. Is a chatbot as well. I think they are using ID coming from MongoDB databases.

You can see in the screenshot above, the connection is dropping stream errors. Sending of messages is not affected, only receiving. WhatsApp will not send the same message to you a hundred times, it cannot afford that.

The error is in acknowledgement, or lack thereof. We need to implement no-acks in the case of decryption failures