Commit c55a529
committed
fix(baileys): expose delivery receipts for group messages
Baileys routes receipts for group messages to `message-receipt.update`
instead of `messages.update` (see `handleReceipt` in messages-recv.ts).
In that branch, delivery arrives as `receiptTimestamp` while read
arrives as `readTimestamp` — but only `readTimestamp` was being
consumed, and `sendDataWebhook` was never called.
The practical effect is that delivery confirmation for group messages
never reaches the webhook. Individual chats confirm normally
(SERVER_ACK, DELIVERY_ACK, READ); groups produce no event at all, even
though WhatsApp does send the receipt and Baileys does receive it — one
per participant.
Verified on 2.3.7 with `LOG_BAILEYS=debug`: a single group message
produced four `tag: "receipt"` stanzas, and zero webhook calls.
This emits MESSAGES_UPDATE using the same flat payload as the
individual-chat branch, so no new event type is needed and existing
consumers keep working — `participant` is already part of the status
schema. The existing `readTimestamp` handling is untouched.1 parent e273b90 commit c55a529
1 file changed
Lines changed: 18 additions & 0 deletions
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2163 | 2163 | | |
2164 | 2164 | | |
2165 | 2165 | | |
| 2166 | + | |
| 2167 | + | |
| 2168 | + | |
| 2169 | + | |
| 2170 | + | |
| 2171 | + | |
| 2172 | + | |
| 2173 | + | |
| 2174 | + | |
| 2175 | + | |
| 2176 | + | |
| 2177 | + | |
| 2178 | + | |
| 2179 | + | |
| 2180 | + | |
| 2181 | + | |
| 2182 | + | |
| 2183 | + | |
2166 | 2184 | | |
2167 | 2185 | | |
2168 | 2186 | | |
| |||
0 commit comments