[BUG] No session found to decrypt message

[oscarguindzberg]

Describe the bug I have a server with 15 connected whatsapp users. I find this on the log from time to time:

{
  "level": 50,
  "time": 1718906974900,
  "pid": 41327,
  "hostname": "ip-xxx-xxx-xxx-xxx",
  "key": {
    "remoteJid": "xxx@g.us",
    "fromMe": false,
    "id": "xxx",
    "participant": "xxx@s.whatsapp.net"
  },
  "err": {
    "type": "Error",
    "message": "No session found to decrypt message",
    "stack": "Error: No session found to decrypt message\n at xxx@g.us::xxx::0 [as awaitable]   
     (/baileys/WASignalGroup/group_cipher.js:54:15)
     at async asyncQueueExecutor (/baileys/WASignalGroup/queue_job.js:20:29)"
  },
  "msg": "failed to decrypt message"
}

To Reproduce Don't know how to reproduce, it happens from time to time on a server with 15 connected whatsapp users.

Expected behavior No errors on the log

Environment (please complete the following information):

• Is this on a server? yes

• What do your connectOptions look like?

  const { version, isLatest } = await fetchLatestBaileysVersion()
  const { state, saveCreds } = await useMultiFileAuthState('myPath')
  const msgRetryCounterCache = new NodeCache()
  
      async function getMessage(key)  {
          if(store) {
              const msg = await store.loadMessage(key.remoteJid, key.id)
              return msg?.message || undefined
          }
          // only if store is present
          return proto.Message.fromObject({})
      }
  
  makeWASocket({
          version,
          logger,
          printQRInTerminal: false,
          mobile: false,
          auth: {
              creds: state.creds,
              keys: makeCacheableSignalKeyStore(state.keys, logger),
          },
          msgRetryCounterCache,
          generateHighQualityLinkPreview: true,
          // ignore broadcast and newsletter messages
          shouldIgnoreJid: jid => !jid || isJidBroadcast(jid) || isJidNewsletter(jid),
          // implement to handle retries & poll updates
          getMessage,
          shouldSyncHistoryMessage: () => true,
          markOnlineOnConnect: false
      })

• Do you have multiple clients on the same IP? yes, 15 clients
• Are you using a proxy? no

Additional context Using baileys v6.7.5

[oscarguindzberg]

These bugs may be related https://github.com/WhiskeySockets/Baileys/issues/885 https://github.com/WhiskeySockets/Baileys/issues/886 https://github.com/WhiskeySockets/Baileys/issues/887 https://github.com/WhiskeySockets/Baileys/issues/888

[ErgashevAkbarjon]

I do have the same issue. Also have multiple connected WA numbers.

[ErgashevAkbarjon]

Maybe it's all because of using already an old and archived(by ForstaLabs) version of libsignal-node package. Maybe it's better to move to official package from signalapp ?

[dephea]

Same issue

[joaosouz4dev]

Same here. "err": { "type": "Error", "message": "No SenderKeyRecord found for decryption", "stack": "Error: No SenderKeyRecord found for decryption\n at <ID>@g.us::<NUM>::0 [as awaitable] (/app/node_modules/@whiskeysockets/baileys/WASignalGroup/group_cipher.js:49:15)\n at async _asyncQueueExecutor (/app/node_modules/@whiskeysockets/baileys/WASignalGroup/queue_job.js:20:29)" }, "msg": "failed to decrypt message" }

[dcpenteado]

Same.

[ramon-victor]

Same