puppet-wechat: Can not login with UOS patch

10:02:16 INFO StarterBot onScan: Scanned(3)
10:02:17 SILL PuppetWeChatEvent onLog(checkScan() code:201 url:https://login.weixin.qq.com/qrcode/gaGsViKqww== scanCode:201)
10:02:18 SILL PuppetWeChatEvent onLog(checkScan() code:201 url:https://login.weixin.qq.com/qrcode/gaGsViKqww== scanCode:201)
10:02:19 SILL PuppetWeChatEvent onLog(checkScan() code:201 url:https://login.weixin.qq.com/qrcode/gaGsViKqww== scanCode:201)
10:02:20 SILL PuppetWeChatEvent onLog(checkScan() code:201 url:https://login.weixin.qq.com/qrcode/gaGsViKqww== scanCode:201)
10:02:21 WARN PuppetWeChatBridge onDialog() page.on(dialog) type:type() {
        return this._type;
    } message:登录失败。
10:02:21 ERR Config ###########################
10:02:21 ERR Config Wechaty unhandledRejection: GError: type() {
        return this._type;
    }(登录失败。)
    at Function.from (file:///node_modules/.pnpm/registry.npmmirror.com+gerror@1.0.16/node_modules/gerror/src/gerror/gerror.ts:69:17)
    at Bridge.onDialog (file:///node_modules/.pnpm/registry.npmmirror.com+wechaty-puppet-wechat@1.11.8_d4744562d843ac589ee1af4a4661bf5c/node_modules/wechaty-puppet-wechat/src/bridge.ts:189:31)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) [object Promise]
10:02:21 ERR Config ###########################
10:02:21 ERR Config process.on(unhandledRejection) promise.catch(type() {
        return this._type;
    }(登录失败。))
Config GError: type() {
        return this._type;
    }(登录失败。)
    at Function.from (file:///node_modules/.pnpm/registry.npmmirror.com+gerror@1.0.16/node_modules/gerror/src/gerror/gerror.ts:69:17)
    at Bridge.onDialog (file:///node_modules/.pnpm/registry.npmmirror.com+wechaty-puppet-wechat@1.11.8_d4744562d843ac589ee1af4a4661bf5c/node_modules/wechaty-puppet-wechat/src/bridge.ts:189:31)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 2,
  details: 'GError: type() {\n' +
    '        return this._type;\n' +
    '    }(登录失败。)\n' +
    '    at Function.from (file:///node_modules/.pnpm/registry.npmmirror.com+gerror@1.0.16/node_modules/gerror/src/gerror/gerror.ts:69:17)\n' +
    '    at Bridge.onDialog (file:///node_modules/.pnpm/registry.npmmirror.com+wechaty-puppet-wechat@1.11.8_d4744562d843ac589ee1af4a4661bf5c/node_modules/wechaty-puppet-wechat/src/bridge.ts:189:31)\n' +
    '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'
}

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 46 (5 by maintainers)

Commits related to this issue

Most upvoted comments

既然新版统信 UOS 和银河麒麟微信仍然基于 electron, 那么我们可以研究下新版 API 的变化

腾讯出了 Linux 版微信~ - V2EX

Same problem, I guess the WeChat login API has changed.

Has there anyone tried to change the WECHATY_PUPPET_WECHAT_TOKEN to a customer new one, to see if it helps?

See

* [Allow users to use their self-generated extspam #142](https://github.com/wechaty/puppet-wechat/pull/142)

通过 BlueSky-07/wechat-token 获取 extspam

My code:

const extspam = GET_FROM('https://github.com/BlueSky-07/wechat-token')
process.env.WECHATY_PUPPET_WECHAT_TOKEN = extspam

WechatyBuilder.build({
    name: 'wechaty-puppet-wechat',
    puppet: 'wechaty-puppet-wechat',
    puppetOptions: {
      token: process.env.WECHATY_PUPPET_WECHAT_TOKEN,
    }
})

Result:

WARN PuppetWeChatBridge onDialog() page.on(dialog) type:type() {
        return this._type;
} message:登录失败。

Versions:

"wechaty": "^1.10.4",
"wechaty-puppet-wechat": "^1.10.5"