[Bug]: Whatsapp

[ThePixelPro366]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Connecting to Whatsapp fails with this: WhatsApp connect error: WhatsApp login failed: status=515 Unknown Stream Errored (restart required)

Steps to reproduce

1. Click on Logout if you are already logged in
2. Click show QR code
3. Scan the QR code with Whatsapp
4. Click wait for scan

Expected behavior

Connectingg

Actual behavior

This error and no login: WhatsApp connect error: WhatsApp login failed: status=515 Unknown Stream Errored (restart required)

OpenClaw version

Newest

Operating system

Android

Install method

No response

Model

openrouter:free

Provider / routing chain

N/A

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

[friuns2]

I will check

[ThePixelPro366]

Hi, I don't know if the update is related to this error, but with the new version the gateway seems to crash if you want to connect with WhatsApp.

[ThePixelPro366]

(It crashes after scanning the QR code with WhatsApp.)

[friuns2]

did old version work for you?

[Mr-Savage1]

I have been trying from a long time whatsapp and telegram don't work I havent tried discord tho but from what i have seen it doesn't work

[friuns2]

Thanks for the extra reports. We are now seeing this as part of a broader channel startup stability problem, not just one QR flow issue.

From recent feedback logs, WhatsApp failures often appear together with gateway startup instability and process restarts. So the likely fix is on the gateway/channel lifecycle side rather than only on the QR scan UI.

Current direction:

1. stabilize gateway startup first
2. reduce restart loops / low-memory kills
3. re-test WhatsApp pairing after that on a clean session

If anyone here can still reproduce it on the latest build, please send a fresh in-app feedback report immediately after scanning the QR code and pressing wait-for-scan. That timing matters because we need the gateway log from the failing pairing attempt itself.

[Mr-Savage1]

I used cli in-app with openclaw and it works