Closed quantumFlame closed 10 months ago
Hi, @quantumFlame! I'm Dosu, and I'm helping the wechaty team manage their backlog. I wanted to let you know that we are marking this issue as stale.
From what I understand, you reported an issue where Wechaty is not receiving messages from official accounts. Currently, there haven't been any updates or comments on this issue.
Before we close this issue, we wanted to check with you if it is still relevant to the latest version of the wechaty repository. If it is, please let us know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days.
Thank you for your understanding and contribution to the wechaty community!
0. Report Issue Guide
Please run the following command and check whether the problem has been fixed:
No. Wechaty itself is running well.
Please search in FAQ List first, and make sure your problem has not been solved before. No similar issues found.
Please search in the issue first, and make sure your problem had not been reported before No similar issues found.
1. Versions
What is your wechaty version? Answer: 0.29.42
Which puppet are you using for wechaty? (padchat/puppeteer/padpro/...) Answer: wechaty-puppet-padplus
What is your wechaty-puppet-XXX(padchat/puppeteer/) version? Answer: 0.3.11
What is your node version? (run
node --version
) Answer: v11.14.0What os are you using Answer: Ubuntu 16.04.6 LTS
2. Describe the bug
Give a clear and concise description of what the bug is. Wechaty does not receive message from official accounts. Instead, it detects the message from itself when communicating with official accounts.
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. In step 3, wechaty should be activated by the message from the official account and print message 'wo shi ting hao de'.
5. Actual behavior
If applicable, add screenshots to help explain your problem. But do not paste log screenshots here. The fromId 'wxid_ofaw2d...' is the robot itself. The toId 'gh_3015...' is the official account.
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: 06:39:41 SILL Config WECHATY_LOG set level to silly 06:39:41 INFO Config registering process.on("unhandledRejection") for development/debug 06:39:41 VERB Config constructor() 06:39:43 VERB Puppet constructor({"token":"puppet_padplus_3f688727dcb631f7"}) #0 06:39:43 VERB StateSwitch constructor(name=PuppetPadplus) 06:39:43 VERB MemoryCard constructor(undefined) 06:39:43 VERB MemoryCard getStorage() for storage type: N/A 06:39:43 VERB MemoryCard load() from storage: N/A 06:39:43 VERB MemoryCard load() no storage 06:39:43 VERB Puppet constructor() watchdog timeout set to 60 seconds 06:39:43 VERB HotImport callerResolve(., /home/tanjin/MetaPuppetForPython/socket_client/node_modules/wechaty-puppet/dist/src/puppet.js) 06:39:43 SILL HotImport callerResolve() callsites() file=/home/tanjin/MetaPuppetForPython/socket_client/node_modules/hot-import/dist/src/hot-import.js, type=Object 06:39:43 SILL HotImport callerResolve() callsites() file=/home/tanjin/MetaPuppetForPython/socket_client/node_modules/wechaty-puppet/dist/src/puppet.js, type=null 06:39:43 SILL HotImport callerResolve() callsites() file=/home/tanjin/MetaPuppetForPython/socket_client/node_modules/wechaty-puppet-padplus/dist/src/puppet-padplus.js, type=null 06:39:43 SILL HotImport callerResolve() callerFile=/home/tanjin/MetaPuppetForPython/socket_client/node_modules/wechaty-puppet-padplus/dist/src/puppet-padplus.js 06:39:43 VERB Puppet constructor() childClassPath=/home/tanjin/MetaPuppetForPython/socket_client/node_modules/wechaty-puppet-padplus/dist/src 06:39:43 VERB PadplusManager constructor() 06:39:43 SILL PadplusManager : StateSwitch { _name: 'PadplusManager', log: { silly: [Function: silly], verbose: [Function: verbose], warn: [Function: warn], error: [Function: error] }, _on: false, _pending: false, offPromise: Promise { undefined }, onResolver: [Function], onPromise: Promise {7. Additional context
Add any other context about the problem here. I suspect that in current code there is a logic that in the communication official accounts are always robots, thus only being activated by messages from the other side. However, this assumption is not always true. The other side could be robots, too.
[bug]