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:
npm install wechaty-puppet-macpro
Please search in the issue first, and make sure your problem had not been reported before
1. Versions
What is your wechaty version?
Answer: 0.28.3
What is your wechaty-puppet-macpro version?
Answer: 0.2.6
What is your node version? (run node --version)
Answer: v10.18.0
What os are you using
Answer: Amazon Linux (a flavor of RedHat)
2. Describe the bug
Give a clear and concise description of what the bug is.
Cannot login.
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:
use token and create a simple script to login with puppet-macpro
4. Expected behavior
Give a clear and concise description of what you expected to happen.
Cannot login and bot is stuck doing nothing.
5. Actual behavior
If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.
See error log
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!
0. Report Issue Guide
1. Versions
What is your wechaty version? Answer:
0.28.3
What is your wechaty-puppet-macpro version? Answer:
0.2.6
What is your node version? (run
node --version
) Answer:v10.18.0
What os are you using Answer: Amazon Linux (a flavor of RedHat)
2. Describe the bug
Give a clear and concise description of what the bug is.
Cannot login.
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:
4. Expected behavior
Give a clear and concise description of what you expected to happen.
Cannot login and bot is stuck doing nothing.
5. Actual behavior
If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.
See error log
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
```shell $ WECHATY_LOG=silly node yourbot.js Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages Answer: 05:12:48 INFO Config registering process.on("unhandledRejection") for development/debug 05:12:48 VERB Config constructor() 05:12:49 VERB Puppet constructor({"token":"puppet_macpro_1dfxxxxxxxxx"}) #0 05:12:49 VERB StateSwitch constructor(name=PuppetMacpro) 05:12:49 VERB MemoryCard constructor(undefined) 05:12:49 VERB MemoryCard getStorage() for storage type: N/A 05:12:49 VERB MemoryCard load() from storage: N/A 05:12:49 VERB MemoryCard load() no storage 05:12:49 VERB Puppet constructor() watchdog timeout set to 60 seconds 05:12:49 VERB HotImport callerResolve(., /home/ec2-user/visa-bot/rasa-wechat-server/node_modules/wechaty-puppet/dist/src/puppet.js) 05:12:49 SILL HotImport callerResolve() callsites() file=/home/ec2-user/visa-bot/rasa-wechat-server/node_modules/hot-import/dist/src/hot-import.js, type=Object 05:12:49 SILL HotImport callerResolve() callsites() file=/home/ec2-user/visa-bot/rasa-wechat-server/node_modules/wechaty-puppet/dist/src/puppet.js, type=null 05:12:49 SILL HotImport callerResolve() callsites() file=/home/ec2-user/visa-bot/rasa-wechat-server/node_modules/wechaty-puppet-macpro/dist/src/puppet-macpro.js, type=null 05:12:49 SILL HotImport callerResolve() callerFile=/home/ec2-user/visa-bot/rasa-wechat-server/node_modules/wechaty-puppet-macpro/dist/src/puppet-macpro.js 05:12:49 VERB Puppet constructor() childClassPath=/home/ec2-user/visa-bot/rasa-wechat-server/node_modules/wechaty-puppet-macpro/dist/src 05:12:49 SILL Accessory #07. Additional context
Add any other context about the problem here.
[bug]