Baileys: [BUG] When sending message

Hello, I’m having this error when trying to send messages to groups.

Failed to decrypt message with any known session... Session error:MessageCounterError: Key used already or never filled MessageCounterError: Key used already or never filled at SessionCipher.doDecryptWhisperMessage (/home/-/-/node_modules/libsignal/src/session_cipher.js:236:19)

I’ve tried to rescan the session and it follows.

I’m using useMultiFileAuthState(‘…’) as stated in the documentation

would anyone know what could be causing this?

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 41 (5 by maintainers)

Most upvoted comments

bad decryption errors are due to some mismanagement in our libsignal, will look into them all

Found the problem, when you connect at the same time with 2 or more devices it gives you ‘bad mac’ error. In my case I was using same connection at the same time with production and development. Solution: Delete all files saved for authentication, and never connect at the same time.

i use same account (sim card) for multiple bots, different scenarios. mycode is responsible for differentiating the types of messages received and sent. local or in another country (aws).

but they all use different auth, i authorized them using qr code, they are different devices from whatsapp connected devices list. even local dev has its own auth to avoid these conflict flags.

I am quite sure that you have a issue with authentication. When there is a conflict WhatsApp blocks everything and throws ‘bad Mac’ error. Try reviewing your authentication code, 90% the issue is there. Probably you overwrite some important file or folder. How do you handle it? Can you share your code?

Found the problem, when you connect at the same time with 2 or more devices it gives you ‘bad mac’ error. In my case I was using same connection at the same time with production and development. Solution: Delete all files saved for authentication, and never connect at the same time.

tive o mesmo erro so verifiquei o jid 9999999999999999999999@g.us para 999999999999-9999999999@g.us

i had the same error so i checked the jid 9999999999999999999999@g.us to 999999999999-9999999999@g.us

A solução é fazer tratamento em grupos. Não é bug do bayleis.

The solution is make processing in groups. not bug of bayleis.

Qual foi a solução para você?

Com certeza é um bug do Baileys…

Esse erro fica aparecendo porque o Baileys não é capaz de lidar com algo e também não mostra como tratar isso… definitivamente não é um comportamento esperado em nenhum software.

A solução é fazer tratamento em grupos. Não é bug do bayleis.

The solution is make processing in groups. not bug of bayleis.

+1