-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Room] COULD NOT GET ROOM FROM ROOM.FINDALL() AFTER ROOM CREATED #32
Comments
I think u should sync room data firstly ...
await room.sync()
await bot.Room.findAll()
... if there still some problems pls call me here. thx |
I do not think the
|
In this case, bot can not get the room payload when the room been created (one bug which has already been resolved.), So it's the reason for this issue, maybe the former response from me is not exact enough. |
So that's a workaround, I understood. Thanks for the explanation. |
You are welcome. |
0. Report Issue Guide
1. Versions
What is your wechaty version?
Answer: 0.28.3
What is your wechaty-puppet-padplus version?
Answer: 0.0.114
What is your node version? (run
node --version
)Answer: v10.15.1
What os are you using
Answer: Darwin wc-macpro-2.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64 x86_64
2. Describe the bug
can't got room from Room.findAll() method after Room.create()
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
got message "got the room just created"
5. Actual behavior
hadn't get messsage "got the room just created"
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
7. Additional context
Add any other context about the problem here.
[bug]
The text was updated successfully, but these errors were encountered: