Baileys [BUG] failure in decrypting message

[BUG] failure in decrypting message

Open jurajmatus opened this issue 1 year ago • 2 comments

Describe the bug Sometimes the message fails to be decrypted and is then represented as an empty stub

Related issues

#1590
#1721

To Reproduce Steps to reproduce the behavior:

I don't see any rule when it happens

Expected behavior Message is decrypted or at least there is a method to retry decryption in case keys are updated later

Environment (please complete the following information):

Is this on a server? YES (node version 14)
What do your connectOptions look like?

{
    version,// fetchLatestBaileysVersion()
    logger: state.logger, // error level
    markOnlineOnConnect: false,
    auth: state.authState, // custom DynamoDB based implementation
    syncFullHistory: true,
    msgRetryCounterMap: state.msgRetryCounterMap,
    connectTimeoutMs: 5 * 60 * 1000,
    defaultQueryTimeoutMs: undefined,
    keepAliveIntervalMs: 10000,
    browser: Browsers.macOS('Desktop'),
  }

Do you have multiple clients on the same IP? NO
Are you using a proxy? NO

Additional context A message like this is produced in messages.upsert:

{
  "key": {
    "remoteJid": "[email protected]",
    "fromMe": true,
    "id": "xx",
    "participant": "[email protected]"
  },
  "messageTimestamp": 1663009678,
  "pushName": "___",
  "status": 2,
  "messageStubType": 2,
  "messageStubParameters": [
    "No sender key for: [email protected]::xx::0"
  ]
}

Sep 13 '22 18:09 jurajmatus

Isso ocorre comigo também.

Sep 13 '22 22:09 undefined-60

To Reproduce: Happen only on groups or statues message.upsert when trying to send a message through a real device. Through Whatsapp web working fine. (In my case)