Please search in FAQ List first, and make sure your problem has not been solved before.
Done
Please search in the issue first, and make sure your problem had not been reported before
Done
1. Versions
What is your wechaty version?
Answer: 0.40.10
What is your wechaty-puppet-donut version?
Answer: 0.8.3
What is your node version? (run node --version)
Answer: 10.16.0
What os are you using
Answer: Ubuntu 18.04.4 LTS in development environment and Cent OS 7.8.2003.
2. Describe the bug
Last night, I logged off from the Windows WeChat through my phone and then logged in when I was trying to test my onReady handler. However, after running for several hours, the login QR code appeared on the terminal and the bot stopped working. I double checked my phone and it seemed that the Windows login was still there. I sent the login message to the BotSentry as usual but received a QR code instead of logging in directly. I scanned the QR code but it had already expired. Then I repeated this procedure for several times but I constantly got the same expired QR code.
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:
I'm not sure how to describe the reproduction of this problem w/o spilling my serect key since it happens in the login phase but here's how I got into this problem:
Login with puppet-donut just as usual by sending a message to BotSentry
Logout from Windows device from WeChat's mobile app
Login with puppet-donut
4. Expected behavior
I should receive a new QR code when I login through the bot.
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!
Sorry about this lengthy log message but I couldn't collapse the log message with code formatting.
0. Report Issue Guide
Please run the following command and check whether the problem has been fixed:
Done
Please search in FAQ List first, and make sure your problem has not been solved before. Done
Please search in the issue first, and make sure your problem had not been reported before Done
1. Versions
What is your wechaty version? Answer: 0.40.10
What is your wechaty-puppet-donut version? Answer: 0.8.3
What is your node version? (run
node --version
) Answer: 10.16.0What os are you using Answer: Ubuntu 18.04.4 LTS in development environment and Cent OS 7.8.2003.
2. Describe the bug
Last night, I logged off from the Windows WeChat through my phone and then logged in when I was trying to test my onReady handler. However, after running for several hours, the login QR code appeared on the terminal and the bot stopped working. I double checked my phone and it seemed that the Windows login was still there. I sent the login message to the BotSentry as usual but received a QR code instead of logging in directly. I scanned the QR code but it had already expired. Then I repeated this procedure for several times but I constantly got the same expired QR code.
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: I'm not sure how to describe the reproduction of this problem w/o spilling my serect key since it happens in the login phase but here's how I got into this problem:
4. Expected behavior
I should receive a new QR code when I login through the bot.
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! Sorry about this lengthy log message but I couldn't collapse the log message with code formatting.
7. Additional context
Everything worked well until I clicked "logged out from Windows device" on my phone.
[bug]