Huan Li
```sh friday@wechaty-contributors:~/git/friday$ npm ls wechaty-puppet-whatsapp [email protected] /home/friday/git/friday └── [email protected] ``` Error log messages: ```sh ... undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined undefined...
I logged in with Puppet WhatsApp once, and then want to start from refresh again. Then I deleted the `ding-dong-bot.memory-card.json`, and started Wechaty again. However, the Bot still has old...
After running for some time, the puppet might not emit the scan event anymore. (maybe due to the current login session has been invalid) Which will stuck the Wechaty bot...
## Reproduce Login to the WhatsApp bot by Wechaty, then on the phone APP, send a message out to a group ## Expected There should be a `message` event for...
Sometimes Friday BOT will lost the session of the WhatsApp and it does not emit `scan` event anymore. After delete the existing invalid `xxx.memory-card.json` file, it can emit `scan` event...
We have a features list at https://wechaty.js.org/docs/puppet-providers/whatsapp/#features-to-be-implemented and it is outdated after we published the [email protected] Need to be updated. @su-chang @hcfw007 Could you please help the community to update...
I saw we are using lots of `log.info(...)` in the puppet code, which is not a necessary message to the end users. We should: 1. Use `warn` when there's something...
 Could you please share the code that send this message? Thank you very much.
Instead set it to `v1.11.57`, it would be better to set it to `v1.11` so that we can continue working on it for the v1.11 version.
Currently, we are using a new branch `dev` without DevOps enabled. I'd like to enable DevOps to each version that passed the CI to NPM. Here are two solutions: 1....