You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All three messages were added within the messagesResult.push(msgs[j]);.
However, in the latest versions of wa-js (v2.25.0) and WhatsApp Web (2.2335.9), only the message "3" retains the isNewMsg property, and the messages "1" and "2" do not have this property anymore.
But in my test case, messages 1 and 2 should have isNewMsg = true because they were sent simultaneously along with message 3.
const chats = await WPP.chat.list(options);
let messagesResult = [];
if (chats) {
try {
for (var i = 0; i < chats.length; i++) {
if (chats[i].unreadCount > 0) { // Verifique se msgs existe
let msgs = await WPP.chat.getMessages(chats[i].id._serialized, {count: -1, onlyUnread: true});
for (var j = 0; j < msgs.length; j++) {
Description
I have implemented the following function:
Previously, in the version of wa-js v2.24.7 with WhatsApp 2.2333.11, if I sent the messages:
1
2
3
using my implementation:
All three messages were added within the messagesResult.push(msgs[j]);.
However, in the latest versions of wa-js (v2.25.0) and WhatsApp Web (2.2335.9), only the message "3" retains the isNewMsg property, and the messages "1" and "2" do not have this property anymore.
But in my test case, messages 1 and 2 should have isNewMsg = true because they were sent simultaneously along with message 3.
Environment
Steps to Reproduce
Log Output
The text was updated successfully, but these errors were encountered: