-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Description
Important:Please file the issue follow the template, or we won't help you to solve the problem.
0. Report Issue Guide
- Please run the following command and check whether the problem has been fixed:
rm -rf package-lock.json
rm -rf node_modules
npm install
-
Please search in FAQ List first, and make sure your problem has not been solved before.
-
Please search in the issue first, and make sure your problem had not been reported before
1. Versions
-
What is your wechaty version?
Answer: Version 7.0.13 -
Which puppet are you using for wechaty? (padchat/puppeteer/padpro/...)
Answer: padchat -
What is your wechaty-puppet-XXX(padchat/puppeteer/) version?
Answer: "wechaty-puppet-padchat": "^0.19.3" -
What is your node version? (run
node --version
)
Answer: v10.12.0 -
What os are you using
Answer: linux
2. Describe the bug
Bot error: Error: PADPLUS_ERROR EXIT 你的微信登录环境存在异常。为了帐号安全,本次登录已失效。
at PuppetPadplus.puppet.on.error (/node_modules/_wechaty@0.31.22@wechaty/dist/src/wechaty.js:439:44)
at PuppetPadplus.emit (events.js:182:13)
at PuppetPadplus.EventEmitter.emit (domain.js:442:20)
at PuppetPadplus.emit (/node_modules/_wechaty-puppet@0.20.1@wechaty-puppet/dist/src/puppet.js:163:22)
at PadplusManager.manager.on (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/puppet-padplus.js:87:22)
at PadplusManager.on.args (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:94:26)
at PadplusManager.emit (events.js:182:13)
at PadplusManager.EventEmitter.emit (domain.js:442:20)
at PadplusManager.emit (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:88:22)
at PadplusManager.<anonymous> (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:450:42)
at Generator.next (<anonymous>)
at /node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:8:71
at new Promise (<anonymous>)
at __awaiter (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:4:12)
at GrpcEventEmitter.grpcGatewayEmitter.on (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/padplus-manager/padplus-manager.js:257:53)
at GrpcEventEmitter.emit (events.js:182:13)
at GrpcEventEmitter.EventEmitter.emit (domain.js:442:20)
at GrpcGateway.<anonymous> (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/server-manager/grpc-gateway.js:460:41)
at Generator.next (<anonymous>)
at /node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/server-manager/grpc-gateway.js:8:71
at new Promise (<anonymous>)
at __awaiter (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/server-manager/grpc-gateway.js:4:12)
at ClientReadableStream.stream.on (/node_modules/_wechaty-puppet-padplus@0.4.5@wechaty-puppet-padplus/dist/src/server-manager/grpc-gateway.js:377:41)
at ClientReadableStream.emit (events.js:182:13)
at ClientReadableStream.EventEmitter.emit (domain.js:442:20)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at ClientReadableStream.Readable.push (_stream_readable.js:219:10)
at Object.onReceiveMessage (/node_modules/_grpc@1.24.2@grpc/src/client_interceptors.js:1263:19)
at InterceptingListener.recvMessageWithContext (/node_modules/_grpc@1.24.2@grpc/src/client_interceptors.js:607:19)
at /node_modules/_grpc@1.24.2@grpc/src/client_interceptors.js:707:14
05:11:14 INFO PadplusManager
=================================================
QRCODE_SCAN MSG : 二维码已过期!
=================================================
3. To Reproduce
This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.
Steps to reproduce the behavior:
- run '...'
- ...
- ...
4. Expected behavior
I want to return a QR code that can be logged in instead of invalid, otherwise I need to restart the robot to scan the code again
5. Actual behavior
If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.
6. Full Output Logs
Set env WECHATY_LOG=silly
in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)
We need full log instead of log screenshot or log fragments!
Show Logs
$ WECHATY_LOG=silly node yourbot.js
Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages
Answer:
7. Additional context
Add any other context about the problem here.
[bug]