In Baileys 5.x a "+" was always added at the beginning of the jids provided to the onWhatsApp method. This was removed later in the 6.x version and has created a subtle problem.
Many phone numbers where correctly verified but for some reason french mobile number (starting with 336 or 337) always returned an undefined result (maybe there were problems with some other countries too, I couldn't verify).
Adding back the "+" (if missing) should fix the problem.
1. counter based event buffer keeps track of the number of blocks that request event processing in buffer
2. event buffer only releases events when the last block completes (i.e. counter = 0)
this approach is far simpler than the promised based garbled crap I wrote, should also prevent the deadlock issues it introduced 🙏
This is a breaking change,
1. three events (chats.set, contacts.set, messages.set) are now just one `messaging-history.set` event
2. no need to debounce for app state sync
3. added a new "conditional" chat update to allow for correct app state sync despite not having the chat available on hand
!BREAKING_CHANGE
This was generally a poor design decision on my part to add something like this -- primarily because it could increment the chat unread counter a 100 times for a single message
!BREAKING_CHANGE
1. this allows all offline notifications to be combined into a batch -- to reduce the number of events being sent out
2. to enable the above, the "message.reaction" event has been made an array. Also removes the need for the "operation" field
3. have also now started processing all events under a single queue to prevent state sync problems
azudin