Baileys: [BUG] "stream errored out" while reading QR or just suddenly!

Current workaround is to specify the version [2,2323,4] like:

const sock = makeWASocket({
        version: [2,2323,4],
        ...
});

Credits: @afeno

version: [2,2323,4],

Run here! tks so much!

@w3nder tks u 2

Use version: [2,2323,4]

@iosahil I am getting this message on: “@adiwajshing/baileys”: “^4.2.0”, {“level”:50,“time”:1686584733824,“pid”:22196,“hostname”:“E41664T”,“node”:{“tag”:“stream:error”,“attrs”:{“code”:“515”}},“msg”:“stream errored out”}

Yeah, @adiwajshing/baileys isn’t robust on this as well. What I did was:

1. Create session using @adiwajshing/baileys
2. Make sure to restart the connection if it disconnects when scanning the QR. An example code to do so would look like:

import makeWASocket, { DisconnectReason, useMultiFileAuthState } from '@adiwajshing/baileys';
import {Boom} from '@hapi/boom';

async function startWA() {
  .... 
  ....

  sock.ev.on('connection.update', async update => {
        // Sends QR code to Telegram Chat using a function sendQR()
        if (update.qr) await sendQR(update.qr);
  
        // Gets connection status
        const {lastDisconnect, connection} = update;
        if (connection) logger.info("Connection Status: ", connection)
        let reason = new Boom(lastDisconnect?.error)?.output?.statusCode
        // Handle reconnection
        if (connection === 'close') {
            if (reason === DisconnectReason.badSession) {
                logger.error(`Bad Session, Please Delete /auth and Scan Again`)
                process.exit()
            } else if (reason === DisconnectReason.connectionClosed) {
                logger.warn("Connection closed, reconnecting....");
                await startWA()
            } else if (reason === DisconnectReason.connectionLost) {
                logger.warn("Connection Lost from Server, reconnecting...");
                await startWA()
            } else if (reason === DisconnectReason.connectionReplaced) {
                logger.error("Connection Replaced, Another New Session Opened, Please Close Current Session First");
                process.exit()
            } else if (reason === DisconnectReason.loggedOut) {
                logger.error(`Device Logged Out, Please Delete /auth and Scan Again.`)
                process.exit()
            } else if (reason === DisconnectReason.restartRequired) {
                logger.info("Restart Required, Restarting...");
                await startWA()
            } else if (reason === DisconnectReason.timedOut) {
                logger.warn("Connection TimedOut, Reconnecting...");
                await startWA()
            } else {
                logger.warn(`Unknown DisconnectReason: ${reason}: ${connection}`);
                await startWA()
            }
        } else if (connection === 'open') {
            logger.info('Opened connection');
        }
  });
}

1. Switch back to @whiskeysockets/baileys
2. Use the created session with @whiskeysockets/baileys.

This is a very vague & temporary work-around that worked for me.

Fixed at https://github.com/WhiskeySockets/Baileys/releases/tag/v6.2.1

In my code, this issue is closely related to the re-calling of startSock when the connection is closed. And it’s possible that the connection always closes after scanning the QR code, and if reconnection is not performed, the aforementioned issue will occur.

if(connection === 'close') {
  // reconnect if not logged out
  if((lastDisconnect?.error as Boom)?.output?.statusCode !== DisconnectReason.loggedOut) {
  startSock()
  } else {
  console.log('Connection closed. You are logged out.')
  }
}

This worked for me. For some reason we need to restart as soon as this error happens, and it’s just a matter of connecting again.

The “startSock()” call in this snippet is related to the provided example.ts. In my case I didn’t need to rewrite any code, just had a bug that was preventing the startSock() from being executed.

In my code, this issue is closely related to the re-calling of startSock when the connection is closed. And it’s possible that the connection always closes after scanning the QR code, and if reconnection is not performed, the aforementioned issue will occur.

if(connection === 'close') {
  // reconnect if not logged out
  if((lastDisconnect?.error as Boom)?.output?.statusCode !== DisconnectReason.loggedOut) {
  startSock()
  } else {
  console.log('Connection closed. You are logged out.')
  }
}