You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run npm run doctor or wechaty run doctor(for docker user), paste output here
Expected behavior
Actual behavior
Steps to reproduce the behavior (and fixes, if any)
Full Output Logs
$ WECHATY_LOG=silly npm run ts-node mybot.ts
# or
$ WECHATY_LOG=silly node dist/mybot.js
Show Logs
Paste the full output logs here with WECHATY_LOG=silly set
# PASTE FULL LOG OUTPUT AT HERE:
[root@izvkxk91ybsenaz wechatserve]# npm run dev>[email protected] dev /root/wxserve/source/wechatserve
> nodemon bin/www
[nodemon] 1.17.5
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node bin/www`
06:06:19 WARN Wechaty on('friend', contact, friendRequest) is DEPRECATED. use on('friendship', friendship) instead
06:06:19 INFO Wechaty start() v0.16.5 is starting...
06:06:19 INFO Wechaty initPuppet() using puppet: puppeteer
请扫描二维码完成登录:
[nodemon] restarting due to changes...
[nodemon] starting `node bin/www`
The text was updated successfully, but these errors were encountered:
Sorry, you did not follow the ISSUE Template, and there's not enough information about your problem.
In order to help us to find the problem out, you should provide all the detail information about the issue. Please make sure you are following the ISSUE Template, answer all the question, and the more important: provide the steps to reproduce the problem.
I'll close this issue. Please re-submit a new issue to provide the information that needed.
Provide Your Network Information
1.北京beijing
Run
npm run doctor
orwechaty run doctor
(for docker user), paste output hereExpected behavior
Actual behavior
Steps to reproduce the behavior (and fixes, if any)
Full Output Logs
$ WECHATY_LOG=silly npm run ts-node mybot.ts # or $ WECHATY_LOG=silly node dist/mybot.js
Show Logs
Paste the full output logs here with
WECHATY_LOG=silly
setThe text was updated successfully, but these errors were encountered: