WhiskeySockets / Baileys

Lightweight full-featured typescript/javascript WhatsApp Web API
https://baileys.whiskeysockets.io/
MIT License
4.1k stars 1.38k forks source link

[BUG] "Message absent from node" on ads #1034

Open martudev opened 2 months ago

martudev commented 2 months ago

Describe the bug Lately I've been receiving many logs with the error message "Message absent from node" which, according to what I've seen, comes mainly from Facebook advertising. As I've seen, this error was fixed before but it keeps happening. I also see that on WhatsApp Web it says "waiting for messages..." and sometimes even when viewing it from my cell phone and answering from there it doesn't reach WhatsApp Web. My question is, would there be any way to fix it or do a fetch to get the message? Thanks! Here its the message log

{
    "key": {
        "remoteJid": "<number>@s.whatsapp.net",
        "fromMe": false,
        "id": "3A930663A..."
    },
    "messageTimestamp": 17258854688,
    "pushName": "Karina",
    "broadcast": false,
    "messageStubType": 2,
    "messageStubParameters": [
        "Message absent from node"
    ]
}

NOTE: Related to the last version I use, I manage baileys as a private repository pointing to master so the last commit with which I provided that log is the following: 767347b38a22f6ff353832f69b3a0847484d0a5c As i see is the last one

Thanks for all the help!!

To Reproduce Steps to reproduce the behavior:

  1. Send a message from fb ad and sometimes see that gets this error

Expected behavior Some retry system or fetch message system

wilsinho8 commented 2 months ago

https://github.com/WhiskeySockets/Baileys/pull/732

martudev commented 2 months ago

@wilsinho8 Thanks for the reply! I recently tried that change and it didn't work for me, if you look at the log I passed above, for some reason I don't know, my messageStubParameters only has one parameter, instead of 2, therefore when I do messageStubParameters[1] it returns undefined and throws an error when doing JSON.parse. Has something similar happened to you? Thanks!!

wilsinho8 commented 2 months ago

@wilsinho8 Thanks for the reply! I recently tried that change and it didn't work for me, if you look at the log I passed above, for some reason I don't know, my messageStubParameters only has one parameter, instead of 2, therefore when I do messageStubParameters[1] it returns undefined and throws an error when doing JSON.parse. Has something similar happened to you? Thanks!!

Detected message absent from node!!

It happened with me too! So far, no solution for this problem. I recommend you join the Baileys discord to keep up with the news

CSFelix commented 2 months ago

I'm facing the same issue. messageStubParameters contains only one element

PurpShell commented 2 months ago

I'm facing the same issue. messageStubParameters contains only one element

are you on the latest version?

Are all of you guys looking at the message upsert array? There should be more than one message

CSFelix commented 2 months ago

I'm facing the same issue. messageStubParameters contains only one element

are you on the latest version?

Are all of you guys looking at the message upsert array? There should be more than one message

Yep, I'm using 6.7.8 Baileys Version and it's into messages.upsert event listener

jfilipe-dev commented 2 weeks ago

Same issue here, I'm using 6.7.9, "messageStubParameters":["Message absent from node"]

piLovr commented 6 days ago

Same Issue here, happened once! on a One-View Message, but the retry by replying to the Message worked. Sus.