Conversation
startWeixinLoginWithQr and waitForWeixinLogin accepted apiBaseUrl but fetchQRCode/poll still used a hardcoded Tencent endpoint. Use the channel-configured base URL so OpenClaw can pair through local iLink Hub gateways. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream source
Exact mirror of Tencent/openclaw-weixin#190 by @jeffkit.
jeffkit/openclaw-weixin:fix/qr-login-respect-api-base-url128dc53a000f389e7da68e1080115252e5b263dd13513aeedafc92d2126963e437fe016cdb9d678e4feec89ff2b40c93578a96f6325bdd536ad9d38eUpstream intent
Use the configured API base URL for QR-code creation and status polling instead of hardcoding the Tencent endpoint.
Local review status
This one-file mirror merges cleanly into the current target and its focused validation, typecheck, and build pass, but it remains a Draft until these findings are addressed:
baseUrlis not plumbed into first-time QR login, so the main configured-login flow can still use the Tencent default;scaned_but_redirect, fetching a replacement QR does not reset the active polling base URL, so the new QR can be polled against the stale redirect host;Original discussion remains on the upstream PR.