search

ehForwarderBot / efb-wechat-slave

A channel for EH Forwarder Bot.
GNU Affero General Public License v3.0
459 stars 62 forks source link

2.0.5首次安装扫描条码并手机确认后可以登入，但随后立即登出要求重新登录，始终无法正常工作。 #118

Closed tonywww closed 2 years ago

tonywww commented 2 years ago

版本信息 Version Info

EH Forwarder Bot Version: 2.1.1
Python version: 3.7.3

Master channel:  2.2.4

Slave channel:    2.0.5

Middleware:  none

问题描述 Describe the bug

重现步骤 To Reproduce

将版本升级到2.0.5，并删除配置目录内blueset.wechat/*.pki文件，重新运行即可重现。 已在Debian 9/10，Ubuntu 20.04, Python 3.7.3/3.9.5下测试过，均有此故障。 -->

截图 Screenshots

Verbose 日志 Log

Verbose 日志 ``` 请在下方贴出您的 Verbose 日志。如果您对隐私有所顾虑，您可以自行 隐去隐私信息、或 GPG 加密至 BD6B65EC00638DC9083781D5D4B65BB1A106200A。 【贴在下面】 2021-09-22 21:09:24,260 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:153) 主端 Telegram Master (blueset.telegram) # 默认配置档案 初始化成功。 2021-09-22 21:09:24,260 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:155) 所有信道均已成功初始化。 2021-09-22 21:09:24,261 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:169) 所有中间件都已初始化。 2021-09-22 21:09:24,261 [INFO]: apscheduler.scheduler (base.start; base.py:166) Scheduler started 2021-09-22 21:09:24,261 [DEBUG]: apscheduler.scheduler (base._process_jobs; base.py:940) Looking for jobs to run 2021-09-22 21:09:24,262 [DEBUG]: apscheduler.scheduler (base._process_jobs; base.py:1016) No jobs; waiting until a job is added 2021-09-22 21:09:24,262 [DEBUG]: telegram.ext.updater (updater._thread_wrapper; updater.py:351) Bot:1234567890:dispatcher - started 2021-09-22 21:09:24,265 [DEBUG]: efb_wechat_slave.vendor.wxpy.api.bot (misc.start_new_thread; misc.py:420) new thread: _listen 2021-09-22 21:09:24,265 [DEBUG]: telegram.ext.updater (updater._thread_wrapper; updater.py:351) Bot:1234567890:updater - started 2021-09-22 21:09:24,265 [DEBUG]: telegram.ext.updater (updater._start_polling; updater.py:585) Updater thread started (polling) 2021-09-22 21:09:24,265 [DEBUG]: telegram.ext.updater (updater._network_loop_retry; updater.py:642) Start network loop retry bootstrap del webhook 2021-09-22 21:09:24,265 [DEBUG]: telegram.ext.updater (updater.bootstrap_del_webhook; updater.py:760) Deleting webhook 2021-09-22 21:09:24,265 [DEBUG]: telegram.ext.updater (updater.start_polling; updater.py:435) Waiting for Dispatcher and polling to start 2021-09-22 21:09:24,266 [INFO]: efb_wechat_slave.vendor.wxpy.api.bot (bot._listen; bot.py:502) : started 2021-09-22 21:09:24,267 [DEBUG]: telegram.ext.dispatcher (dispatcher.start; dispatcher.py:466) Dispatcher started 2021-09-22 21:09:24,362 [DEBUG]: telegram.ext.updater (updater._start_polling; updater.py:594) Bootstrap done 2021-09-22 21:09:24,362 [DEBUG]: telegram.ext.updater (updater._network_loop_retry; updater.py:642) Start network loop retry getting Updates 2021-09-22 21:09:25,349 [DEBUG]: itchat (login.sync_check; login.py:355) Unexpected sync check result: window.synccheck={retcode:"1101",selector:"0"} 2021-09-22 21:09:25,353 [DEBUG]: plugins.blueset.wechat.WeChatChannel (__init__.exit_callback; __init__.py:263) Calling exit callback... 2021-09-22 21:09:25,354 [DEBUG]: efb_telegram_master.slave_message (slave_message.send_message; slave_message.py:90) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Slave message delivered to ETM. >@ [Text]: 微信服务器已将您登出，请在做好准备后重新登录。; __reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa> 2021-09-22 21:09:25,354 [DEBUG]: efb_telegram_master.chat_object_cache (chat_object_cache.update_chat_obj; chat_object_cache.py:146) Trying to update key ('blueset.wechat', '__ews_user_auth__') with object . Full update: False 2021-09-22 21:09:25,355 [DEBUG]: efb_telegram_master.chat_object_cache (chat_object_cache.update_chat_obj; chat_object_cache.py:148) Key ('blueset.wechat', '__ews_user_auth__') is not in cache. Do compound enrol. 2021-09-22 21:09:25,355 [DEBUG]: efb_telegram_master.chat_object_cache (chat_object_cache.compound_enrol; chat_object_cache.py:53) Compound enrol 2 members of 2021-09-22 21:09:25,356 [DEBUG]: efb_telegram_master.chat_object_cache (chat_object_cache.enrol; chat_object_cache.py:65) Enrolling key ('blueset.wechat', '__ews_user_auth__') with value 2021-09-22 21:09:25,358 [DEBUG]: peewee (peewee.execute_sql; peewee.py:3132) ('SELECT "t1"."slave_uid", "t1"."master_uid" FROM "chatassoc" AS "t1" WHERE ("t1"."slave_uid" = ?)', ['blueset.wechat __ews_user_auth__']) 2021-09-22 21:09:25,358 [DEBUG]: efb_telegram_master.slave_message (slave_message.get_slave_msg_dest; slave_message.py:244) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] The message should deliver to None 2021-09-22 21:09:25,358 [DEBUG]: efb_telegram_master.slave_message (slave_message.get_slave_msg_dest; slave_message.py:252) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Message is in chat 2021-09-22 21:09:25,358 [DEBUG]: efb_telegram_master.slave_message (slave_message.get_slave_msg_dest; slave_message.py:264) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Message is sent to Telegram chat 987654321, with header "💬💻 EWS 用户登录:". 2021-09-22 21:09:25,358 [DEBUG]: efb_telegram_master.slave_message (slave_message.slave_message_text; slave_message.py:317) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Sending as a text message. 2021-09-22 21:09:25,819 [INFO]: efb_wechat_slave.vendor.wxpy.api.bot (bot._listen; bot.py:522) : stopped 2021-09-22 21:09:26,051 [DEBUG]: efb_telegram_master.slave_message (slave_message.slave_message_text; slave_message.py:337) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Processed and sent as text message 2021-09-22 21:09:26,051 [DEBUG]: efb_telegram_master.slave_message (slave_message.dispatch_message; slave_message.py:219) [__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa] Message is sent to the user with telegram message id 987654321.56789. 2021-09-22 21:09:26,052 [DEBUG]: peewee (peewee.execute_sql; peewee.py:3132) ('BEGIN', None) 2021-09-22 21:09:26,052 [DEBUG]: efb_telegram_master.db (db.add_or_update_message_log; db.py:413) [987654321.56789] Received message logging request of __reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa 2021-09-22 21:09:26,055 [DEBUG]: peewee (peewee.execute_sql; peewee.py:3132) ('SELECT "t1"."master_msg_id", "t1"."master_msg_id_alt", "t1"."slave_message_id", "t1"."text", "t1"."slave_origin_uid", "t1"."slave_origin_display_name", "t1"."slave_member_uid", "t1"."slave_member_display_name", "t1"."media_type", "t1"."mime", "t1"."file_id", "t1"."file_unique_id", "t1"."msg_type", "t1"."pickle", "t1"."sent_to", "t1"."time" FROM "msglog" AS "t1" WHERE ("t1"."master_msg_id" = ?) LIMIT ? OFFSET ?', ['987654321.56789', 1, 0]) 2021-09-22 21:09:26,057 [DEBUG]: efb_telegram_master.db (db.add_or_update_message_log; db.py:430) [987654321.56789] Message record is not found in database, insert it 2021-09-22 21:09:26,057 [DEBUG]: peewee (peewee.execute_sql; peewee.py:3132) ('INSERT INTO "msglog" ("master_msg_id", "master_msg_id_alt", "slave_message_id", "text", "slave_origin_uid", "slave_member_uid", "media_type", "mime", "file_id", "file_unique_id", "msg_type", "pickle", "sent_to", "time") VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)', ['987654321.56789', None, '__reauth__.aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa', '微信服务器已将您登出，请在做好准备后重新登录。', 'blueset.wechat __ews_user_auth__', 'blueset.wechat __ews_user_auth__ __ews_user_auth__', 'Text', None, None, None, 'Text', , 'blueset.telegram', datetime.datetime(2021, 9, 22, 21, 9, 26, 57034)]) 2021-09-22 21:09:26,057 [DEBUG]: efb_telegram_master.db (db.add_or_update_message_log; db.py:449) [987654321.56789] Database insert/update outcome: 1 【贴在上面】 ```

备注 Additional context

conan81412B commented 2 years ago

遇到了同样的问题，启动 EFB 后微信 Android 版不显示「网页版已登录」，而且以下三个过程在 Telegram 主端不断循环，无法正常工作：

微信服务器已将您登出，请在做好准备后重新登录。
请在手机上确认。
登录成功。

区别在于我的 WeChat Slave 之前一直可以正常工作，并不是全新安装，而且微信网页版可以正常登录，并没有发生账号封禁。 近期可能有影响的操作是在微信 Android 版将手机号从 +86 更换成了 +1，但没有出现 / 同意任何「服务器账户迁移」的相关条款，一直位于中国大陆区。 

您正在使用 EFB Telegram 主端 2.2.4，运行于默认配置档案与实例、EFB 版本 2.1.1。
已激活 1 个从端：
- 💬 WeChat Slave (blueset.wechat, 2.0.5)

Android 版微信 8.0.2（Google Play）

tonywww commented 2 years ago

我的wechat slave也不是新装，之前和升级到2.0.5后一直工作正常，只是偶然删除了blueset.wechat/*.pki文件后才出现此故障。一度怀疑是微信被限制，但用相同IP登录微信网页版本一切正常，后来试验了多次，直到降级为2.0.4才恢复正常。

conan81412B commented 2 years ago

我的wechat slave也不是新装，之前和升级到2.0.5后一直工作正常，只是偶然删除了blueset.wechat/*.pki文件后才出现此故障。一度怀疑是微信被限制，但用相同IP登录微信网页版本一切正常，后来试验了多次，直到降级为2.0.4才恢复正常。

WeChat Slave 降级到 2.0.4 后已经恢复正常了，非常感谢~

blueset commented 2 years ago

Merging to #126