Message send reports success and returns message ID, but message is not actually delivered (v1.34.7)

[izofis]

Issue Description

Problem Description
After upgrading to v1.34.7 (Latest), message sending behaves incorrectly:

The send operation is reported as successful.
A message ID is returned.
However, the message is not delivered to the recipient.
The same message is also not visible in the sender’s own WhatsApp chat history.
This behavior started appearing with v1.34.7.

Reproduction Steps

Steps to Reproduce

Run the client with v1.34.7 (Latest).
Ensure the session/client is in a ready/connected state.
Trigger a send message operation to any recipient.
Observe that the API/process reports success and returns a message ID.
Check the recipient account: the message is not received.
Check the sender account chat: the same message is not present there either.
Repeat with different recipients; the same behavior persists.

Code Sample

sentMessage = await client.sendMessage(messageto, messagedata, { sendSeen: true });

User Setup

WhatsApp	Type
Account Type	Standard
Authentication Strategy	RemoteAuth
WhatsApp Web Version	000000000000000
whatsapp-web.js Version	1.34.7

Environment	Version
Browser Type	Chrome
Browser Version	000000
Phone OS Version	Andoid
Running OS Version	Ubuntu 24
Node.js Version	v20.19.5

Checklist

• I use the latest released version of whatsapp-web.js.
• I have searched existing issues and confirmed this is not a duplicate.
• I have verified this is a library issue, not a problem with my code.

[Wissam-Elias]

I’m facing the same issue as well:
#201731

[robbchan]

same here

[vhomeDayByDay]

same here, any solution？

[izofis]

Try this. #201733

[Wissam-Elias]

@izofis The solution doesn’t work for me. still the same issue exists

[robbchan]

Try this. #201733

Doesn't work for me.

[BenyFilho]

@Adi1231234

[izofis]

Session poisoning issue only affects accounts sending messages when PR #182677 is active during the initial release of v1.34.7.

If you are still experiencing problems after applying the fix,

you need to keep the session fresh:

• client.logout()
• Delete the session file
• Re-authenticate with QR code

I recommend trying it this way.

@robbchan @Wissam-Elias

[izofis]

{
port: 9221,
info: {
widFromMeUser: 'XXXXX@c.us',
socketState: 'OPENING',
socketStream: 'DISCONNECTED',
hasSynced: true,
wsReadyState: null,
connWid: null,
pushname: 'XXXX',
platform: 'android',
url: 'https://web.whatsapp.com/'
}
}
I checked the status of my system with the console log and got the following output; it acts like the connection exists but doesn't. The system works when I do this: closing and reopening the browser. This doesn't happen in versions before 1.34.7. I'm trying to investigate the reason for this, but my knowledge isn't sufficient. Could you please help me with this? @BenyFilho

[Adi1231234]

Thanks! I’ll check this out and update you soon @izofis @BenyFilho

[BenyFilho]

Thanks! I’ll check this out and update you soon @izofis @BenyFilho

@Adi1231234 don't do anything.
This issue was completely changed. The initial subject was about cipher messages.
@izofis Please, open another issue if you need it.