found a bug #603
|
So when I doing testing over API, I found a bug which is supposed to be that you sent message to someone; the first message either sent or not depending on the recipient, but if the recipient never replied the chat, the message kept on failing to send. But when i replied to the WhatsApp chat window from the recipient's device, it resolved and i have tested this same thing on about 4 to 5 devices |
Replies: 1 comment
|
Hi @RamizMohammad — what you're describing (first message to a recipient silently fails or shows as sent but never arrives, and only starts working after they reply once) is a known issue we're tracking in #830 — First message to a brand-new contact sometimes never arrives. Short version: it's not an OpenWA bug per se — WhatsApp applies a server-side "reach-out" trust policy to the very first message a number sends to someone it has never talked to, and that decline happens after the message leaves OpenWA (which is why the API honestly returns success). It's the same symptom across multiple reporters. If you can drop your OpenWA version, engine, hosting type (datacenter vs residential IP), and account age into #830 using the repro template in the issue body, that'd genuinely help narrow down the mitigation work. Closing this discussion in favour of the tracking issue — please continue there. 🙂 |
Hi @RamizMohammad — what you're describing (first message to a recipient silently fails or shows as sent but never arrives, and only starts working after they reply once) is a known issue we're tracking in #830 — First message to a brand-new contact sometimes never arrives.
Short version: it's not an OpenWA bug per se — WhatsApp applies a server-side "reach-out" trust policy to the very first message a number sends to someone it has never talked to, and that decline happens after the message leaves OpenWA (which is why the API honestly returns success). It's the same symptom across multiple reporters.
If you can drop your OpenWA version, engine, hosting type (datacenter vs residential IP)…