Rajeh Taher

> Any chance this works on MD? Haha, no. This would only fetch messages stored in the storage of a linked device. No fetching from phone

Hmm, please provide us with more information, is this happening after or before you gracefully close the Node app?

a message.react event should be added i think, since a reaction is another type of "message" and it can mess a lot of dialogs up.

guessing this is a rate limit thing, take the messages in incremental bites (like get 50 and delay, and then repeat)

Seems like we should work on pagination or a delay functionality

> > in error it seems like you try to react a message, but in your code it is not integrated. > > `at async Message.react (/app/node_modules/whatsapp-web.js/src/structures/Message.js:344:9)` > > I'm...

whatsapp-web.js is the best for headless right now because of the simple object-oriented approach. https://github.com/pedroslopez/whatsapp-web.js

hi, this seems to be related to this #1359, I'll close this one in favor of that

> I don't know if will help, but when you set any event, each will instantiate another chromium, at least that's what is happening to me > >  >...

This pull request lacks the proper guidelines to be pushed. 1. It lacks testing 2. It lacks type declarations (in index.d.ts)