Technical Support

If you encounter issues while using ClawPilot, contact us at:

• Email: yanghangbin@gmail.com

What to Include in Your Report

• App version
• iOS version
• Time when the issue happened
• Reproduction steps
• Screenshots (if available)

FAQ

1. App cannot connect to Gateway

• Confirm that the Gateway address is reachable.
• Verify the Gateway URL uses wss:// (recommended for production/public network access).
• Check whether the pairing code has expired.
• Check whether your network blocks WebSocket connections.
• If you use wss, make sure the TLS certificate is valid and matches the domain.
• If you changed gateway domain or port, remove the old gateway config in the app and add it again.

2. Push notifications are not received

• In ClawPilot settings, trigger notification-related setup first and verify it is enabled in app.
• Check iOS notification permission for ClawPilot (banner, sound, badge).
• Check Focus mode, Do Not Disturb, and Low Power Mode, which may affect delivery/display.
• If you just changed pairing/notification settings, wait about one minute and test again.

3. OpenClaw settings changes do not take effect

• Some settings require a Gateway restart. Restart OpenClaw Gateway after applying changes.
• Confirm you are editing the same Gateway instance that the app is currently connected to.
• After model/tool/permission updates, test in a new session to avoid old context impact.
• If still not effective, disconnect and reconnect the gateway in app and test again.

4. Gateway pairing fails with pairing_required / unauthorized

• Approve the device request on the Gateway side first.
• If pairing code is time-limited, generate a fresh code and retry.
• Confirm protocol, domain, and port in app are exactly the same as the deployed gateway.
• If the same device fails repeatedly, remove old gateway config and pair again.

5. Message keeps loading or response stops midway

• Check whether Gateway service is still running.
• Check whether your model provider is available (API key, quota, regional network restrictions).
• Check network stability for WebSocket long connections (common in proxy/corporate networks).
• Try a short prompt in a new session to isolate session-specific issues.

6. Session list or history looks incomplete

• Pull to refresh in session drawer and wait for history sync.
• Switch to another session and switch back to trigger reload.
• Confirm you are connected to the intended Gateway instance (avoid environment mismatch).
• If you recently reset session or cleared data, verify state from Gateway side.

7. Connection issues after app update

• Fully close and reopen the app, then reconnect the current Gateway.
• Verify compatibility between app version and Gateway version.
• If issue persists, remove and re-add the gateway config.
• Include app version, gateway version, and exact error message in your report.