Ahmad Syauqi
Ahmad Syauqi
> ```ts > sock.ev.on('connection.update', async({ connection, lastDisconnect, receivedPendingNotifications }) => { > const status = lastDisconnect?.error?.output?.statusCode > > if (connection === 'close'){ > const reason = Object.entries(DisconnectReason).find(i => i[1] ===...
> Message absent from node, most probably a bug from WA itself, especially when it comes to adreply (advertising link from FB) message. > > Just to clarify, you can...
For this type of logout reason you need to restart the socket
I also see this happening in normal conversation and no idea what causes it. Sometimes a connected number can send twice up to many same messages consecutively  This is...
For chats you should use labels.association event ``` conn.ev.on("labels.association", async event => { // handle here }); ```
Show your code for more context
> This dirty trick might help > > ```ts > if(events['messages.upsert']) { > client.sendPresenceUpdate('unavailable') > ``` If there are high number of incoming messages, will it cause any issue due...
Just add `markOnlineOnConnect: false` in your auth configuration. ``` const WA = makeWASocket({ auth: state, ..., markOnlineOnConnect: false, }); ```
> > Just add `markOnlineOnConnect: false` in your auth configuration. > > ``` > > const WA = makeWASocket({ > > auth: state, > > ..., > > markOnlineOnConnect: false,...