-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] Receiving invalid message from events['messages.upsert'] #132
Comments
up |
#oot |
anyone know to solve this issue ?? |
I am facing the same issue here. Some of the numbers initiating their messages seems to have the "Message absent from node" issue, and the text message is not available. Any pointers on how to solve such issue? |
are you guys not getting the message later? it's just failed on first decryption or else and will be retried. you'll get the message later after successful decryption or retry, in my case the longest take +- 5 seconds. |
I am not getting any message later, and also not getting any retries. The sender sent the second message and still get the similar "Message absent from node" issue. But after asking the sender to add our number as contact, the third message is able to be retrieved. However, it would be impossible to ask all our users to add our number as contact. How do you manage to retrieve the decrypted message? |
are you messing with auth keys? are you using useMultiFileAuthState or custom storage? i don't do any fancy code, but the incoming message will be retried and available some time later, this happen few minutes ago and i have it few seconds later. |
I run the Baileys node with the --no-store option because the store writing is taking up much server resources and eventually slows down the server. Do I need to enable store in order for the retry to work? |
Message absent from node, most probably a bug from WA itself, especially when it comes to adreply (advertising link from FB) message. Just to clarify, you can compare the actual message that appears on our device but not on web WA. When this happens, Bailey will not be able to decrypt the message since it is already broken within web WA itself. The situation is completely different when sending a message through baileys. We have a function to retry and resend the failed message. |
@azudindaem Just to confirm, can I say that for now this issue is still an unknown, and there is no way for us to retrieve the actual message in Baileys when we get the "Message absent from node" response, correct? |
UP |
guys, disappearing message aren't the same issue – they aren't even an issue. |
up |
2 similar comments
up |
up |
Investigating, been noticing this more and more EDIT 1: It seems the message retry system itself is failing |
I am getting this for new chats too. It seems random. The retry system sometimes works and sometimes not. |
I don't know if it's the same problem but here the ev['messages.upsert'] out of nowhere stops working and sometimes even restarting the application it still doesn't receive the messages only after restarting several times it works fine again, but it's a bug that has happened frequently |
Out of topic, you need to restart frequently |
Same thing here. i am working on a proper fix for the retry system so I am getting a few logs from some clients who have this issue. We'll work on this and get it just as pristine as the official whatsapp web app |
Hello friend @PurpShell .Did you get any solution on this, I'm having a lot of problems with some customers |
Has anyone got progress on this? |
Solution found, fixing. EDIT: NEW PR OUT #554 |
Does this means if first we were getting a message absent from node, baileys will retry to decrypt again and send another upsert event when it was successful? |
after testing on active fbads there are still appear {
"messages": [
{
"key": {
"remoteJid": "[email protected]",
"fromMe": false,
"id": "C667337FC2A7xxxx"
},
"messageTimestamp": 1703033961,
"pushName": "xxx",
"broadcast": false,
"messageStubType": 2,
"messageStubParameters": [
"Message absent from node"
]
}
],
"type": "notify",
"jid": "[email protected]",
"hasNewMessage": true
} |
It will send a message.update! |
It works very nice, thanks you @PurpShell |
When a new version with this PR is release? |
Describe the bug
A clear and concise description of what the bug is.
On events['messages.upsert'] I got invalid message content with structure like this :
{
"key": {
"remoteJid": "[email protected]",
"fromMe": false,
"id": "sensored"
},
"messageTimestamp": 1686622027,
"pushName": "My Customer Name",
"messageStubType": 2,
"messageStubParameters": [
"Message absent from node"
]
}
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Message content displayed are appropriate on whatsapp (only normal text)
Environment (please complete the following information):
Is this on a server? yes
What do your
connectOptions
look like?const sock = makeWASocket({
version: [2,2323,4],
printQRInTerminal: true,
patchMessageBeforeSending: (message) => {
const requiresPatch = !!(
message.buttonsMessage ||
message.templateMessage ||
message.listMessage
);
if (requiresPatch) {
message = {
viewOnceMessage: {
message: {
messageContextInfo: {
deviceListMetadataVersion: 2,
deviceListMetadata: {},
},
...message,
},
},
};
}
return message;
},
auth: state,
markOnlineOnConnect: false,
generateHighQualityLinkPreview: true,
shouldIgnoreJid: jid => isJidStatusBroadcast(jid),
defaultQueryTimeoutMs: undefined
});
Do you have multiple clients on the same IP? no
Are you using a proxy? no
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: