Skip to content
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

The QR Code will not emit when there's a existing invalid .memory-card.json data. #347

Open
huan opened this issue Apr 1, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@huan
Copy link
Member

huan commented Apr 1, 2022

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 again.

Need to be investigated / fixed.

@huan huan added the bug Something isn't working label Apr 1, 2022
@su-chang
Copy link
Member

su-chang commented Apr 1, 2022

Thank you for your feedback, I will check it later.

@huan
Copy link
Member Author

huan commented Apr 1, 2022

You are welcome. I believe this should be treated as a major issue because it will block production usage and prevent the wechaty from self-recovering.

@su-chang
Copy link
Member

su-chang commented Apr 6, 2022

You are welcome. I believe this should be treated as a major issue because it will block production usage and prevent the wechaty from self-recovering.

It seems that this case related to: #331 or not?

@huan
Copy link
Member Author

huan commented Apr 6, 2022

No, I think this case is not related to #331

For the latest version, I have ran into a very similar issue:

If I logged in a Wechaty program on WhatsAppfollowed by:

  1. Ctrl+C
  2. deleted the MemoryCard data file, and
  3. logged the WhatsApp session out from my Phone App
  4. Restart the Wechaty program

Then the program will not be able to emit the QR Code anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants