Description

BlueBubbles (iMessage) channel stops receiving inbound messages after upgrading from 2026.2.26 to 2026.3.1. Rolling back to 2026.2.26 immediately restores message delivery.

Environment

• OS: macOS 26.3 (arm64)
• Node: v22.22.0
• Working version: 2026.2.26
• Broken version: 2026.3.1
• BlueBubbles server: macOS 26.3.0, Private API enabled
• Gateway bind: loopback (127.0.0.1:18789)

Symptoms

• BlueBubbles provider starts successfully: BlueBubbles webhook listening on /bluebubbles-webhook
• openclaw channels status --probe reports BB as running, connected, works
• BlueBubbles server is running and receiving messages (confirmed via BB REST API)
• BB webhook is correctly registered pointing to http://127.0.0.1:18789/bluebubbles-webhook?password=...
• No inbound messages are delivered to the agent
• Health monitor restarts BB provider every 30 minutes (reason: stuck)
• BB server logs show Status Text: Method Not Allowed when attempting webhook delivery

HTTP behavior (both versions)

GET  /bluebubbles-webhook → 200
POST /bluebubbles-webhook → 405 Method Not Allowed

Note: POST returns 405 on both 2026.2.26 and 2026.3.1, so the actual message delivery mechanism may not be a plain HTTP POST webhook. However, messages flow correctly on 2026.2.26 and stop entirely on 2026.3.1.

Reproduction

1. Configure BlueBubbles channel with webhook on loopback gateway
2. Confirm messages work on 2026.2.26
3. Upgrade to 2026.3.1 (npm install -g [email protected])
4. Restart gateway
5. Send an iMessage to the configured BB number
6. Message never reaches the agent; health monitor reports stuck

Workaround

Roll back: npm install -g [email protected] and restart gateway.

Suspect changes in 2026.3.1

• "Gateway/Container probes: add built-in HTTP liveness/readiness endpoints" — new HTTP route handling
• "Gateway/WS security: keep plaintext ws:// loopback-only by default" — tightened security defaults
• "Telegram/DM topics" — routing changes that may have side effects on other channels

Config

BlueBubbles channel config is unchanged between working and broken state (verified via config backup diffs). Only the OpenClaw version changed.