v0.30.2

Added

• Report poll votes as poll.vote on Baileys, as whatsapp-web.js already does. A vote is read while the poll's creation message is still in the session's message store (BAILEYS_MESSAGE_STORE_LIMIT); earlier votes are not backfilled (#2063). Thanks @Shreyas1702003 for the report.

Fixed

• whatsapp-web.js: an entry WhatsApp Web keeps in a chat that nobody sent (a group or security notice, or a kind the library does not list that carries neither text nor media) is no longer stored or announced as an unknown message, returned by the chat history, seeded as an empty status or reported as a chat's last message (#2076). Thanks @OneArmArmy for the report.
• whatsapp-web.js: the chat history returns a message deleted for everyone under the id the message had, where it returned the id of the delete notice, so it no longer shows beside its stored copy (#2076).
• whatsapp-web.js: GET /sessions/{sessionId}/channels/{channelId}/messages no longer returns a deleted channel update as an entry with an empty body (#2077). Thanks @OneArmArmy for the report.
• Dashboard: a message deleted for everyone is shown once in the chat window of a whatsapp-web.js session, where the stored row and WhatsApp Web's own placeholder for it were both drawn (#2076).
• Dashboard: an entry with nothing to show no longer draws an empty bubble: an unknown message with no text, media or quote in the chat window, or a channel update with neither text nor media in the Channels tab (#2076, #2077).
• Dashboard: a message known only from WhatsApp Web's history no longer shows read ticks, since the history carries no delivery status.
• ctx.mappings.get and ctx.mappings.getByProvider report the handover a plugin instance holds for a chat across its @lid and phone rows (human, else closed, else bot), so a plugin reading one row no longer misses a takeover recorded under the other.
• Store the contact statuses WhatsApp delivers to some Baileys accounts as a top-level <status> stanza, which 0.30.1 acknowledged and dropped: scripts/patch-baileys-status-ack.js now decodes a stanza shaped as the status message it replaces, so it reaches the status list and the status.received webhook. A status that fails to decrypt is dropped, not retried (#2064). Thanks @damar-glh for the report.
• A Baileys message or status that decrypts only in part and is left with no content is no longer stored or announced as an empty unknown message, so a redelivery that carries the content is not skipped as a duplicate.
• A status the account posted is no longer listed among contact statuses on Baileys when WhatsApp names its poster by the account's lid.
• Cap poll.vote at 32 selectedOptions of 1024 characters each and pollName at 1024 characters on both engines, as an inbound poll already is.
• Read a contact's encrypted edit or reaction on Baileys when its key names one party by lid and the other by phone number without the alternate id, using the pairing the session already holds.