Repository navigation
fix: 修复公众号扫码登录被重复换码作废 - #203
Merged
Merged
Conversation
mp 后台记住微信账号后会默认进入「微信快捷登录」,主文档二维码被隐藏; 旧实现找不到二维码时兜底截整页,前端展示没有二维码的页面截图并等待超时。 - 自动点「扫码登录」切回二维码模式,且一轮只切一次:重复切换会重建 登录会话并把用户刚扫的码作废为「已失效」 - 截图需通过二维码识别校验后才保存,不再用整页截图兜底 - 二维码过期/加载失败时点遮罩内「点击刷新」重新出码 - whoami 把快捷登录视图也视为登录页已就绪 - 补充回归测试与已知问题说明
Collaborator
|
感谢修复和详细验证记录!已审查确认取消整页截图兜底、只切一次扫码视图,以及避免扫码成功后重新生成二维码的方向正确。PR 的 Windows/Linux 等 CI 已通过;本轮另用隔离 DOM/替身复现并准备补修:按钮异步出现前不能提前用掉切换机会;跳过隐藏/未加载二维码并保留原有二维码选择器;过期遮罩只点击明确的“点击刷新”,不点击帮助或“重新扫码”,有扫码成功状态时不刷新。 整合 #201/#203 后相关回归 327 passed,覆盖公众号、头条、小红书、知乎、视频号、账号身份、登录生命周期及共享二维码保存,新增 11 项边界用例。会话保存/释放后才写 success、重复启动不打断当前公众号登录的边界保留。作者的真实扫码结果作为报告参考,本轮未调用真实账号或平台发布。 准备合并并带上以上补修及说明文档,感谢贡献! |
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
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.
问题
微信公众号扫码登录无法完成:Web 弹窗里要么显示一张没有二维码的整页截图,要么扫码后手机提示「登录失败:二维码已失效」,后端等待 240 秒后超时报「二维码超时未扫」。
根因
<img>被隐藏(登录码在open.weixin.qq.com的 iframe 里,或需要点「扫码登录」才出现)。旧实现只在主文档找二维码,找不到就兜底截整页,前端展示的是 414KB 的整页截图,里面并没有二维码。startlogin重建登录会话并生成新码,前一张码立即作废。实测日志中getqrcode从 2 变 3,用户扫到的正是被作废的那张,手机因此提示「二维码已失效」。改动
_ensure_qr_mode():检测不到二维码时自动点「扫码登录」切回扫码模式,且一轮只切一次,避免重建会话作废刚扫的码。_capture_qr():用共享的login_qr.save_qr()校验截图里确实能识别出二维码才落盘(并放大到 360px、补白边),删除整页截图兜底;识别不到就明确报错,不再假报qr_ready。_refresh_expired_qr():仅在二维码过期/加载失败遮罩出现时点「点击刷新」,不会误点「扫码成功」旁的「重新扫码」而取消登录。whoami把快捷登录视图也视为登录页已就绪,避免误报「页面未就绪」。验证
t=105s页面进入「扫码成功」,t=109s拿到/cgi-bin/home?...&token=...;whoami返回loggedIn: true,Web 账号状态为已登录。测试计划
pytest tests/test_mp_login.py tests/test_account_login_fixes.py tests/test_account_whoami.py tests/test_login_qr.py(227 passed)