openclaw - 💡(How to fix) Fix Android: unknown requestId error during pairing (Advance Setup, no Google Play) [1 participants]

[openclaw] Failed to start CLI: GatewayClientRequestError: unknown requestId at GatewayClient.handleMessage (file:///Users/lr/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/client-D-67f4NF.js:604:25) at WebSocket.<anonymous> (file:///Users/lr/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/client-D-67f4NF.js:287:35)

TL;DR

The issue may be resolved by ensuring the requestId is correctly propagated and recognized by the Gateway during the WebSocket connection step.

Guidance

• Verify that the requestId generated during the QR code exchange is correctly passed to the Android app and stored for later use in the WebSocket connection.
• Check the Gateway's logs for any errors or warnings related to the requestId validation to understand why it's being reported as "unknown".
• Review the WebSocket connection establishment code in the Android app to ensure it correctly sends the requestId to the Gateway for validation.
• Consider adding logging or debugging statements in the Android app and Gateway to trace the requestId from generation to validation, helping identify where it might be lost or corrupted.

Example

No code example is provided due to the lack of specific implementation details in the issue description.

Notes

The solution might involve adjustments to how the requestId is handled in the Android app or the Gateway, but without more specific details on the implementation, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by thoroughly reviewing and debugging the requestId handling in the Android app and Gateway to identify and fix the propagation or validation issue, as upgrading to a potentially fixed version is not explicitly mentioned as an option in the provided context.