-
Notifications
You must be signed in to change notification settings - Fork 16
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
WPP_Whatsapp module fails to send after continuous operation for a while - Unknown cause #52
Comments
I suspect the reason for the changes in the WhatsApp Web version. I tried using version 2024_09_01_-11:11:55: - INFO - task_sender_session: WhatsApp WEB version: 2.3000.1016139049, which requires alpha.html, but I couldn't find it. Is there any way to resolve the issue of version changes during long-term use? |
as logs:
in so you need know why browser need Authentication after 3h |
I am not sure why the browser where WhatsApp is located requires authentication after 3 hours; I don't know if it's due to WhatsApp Web being active for a long time, or possibly due to WhatsApp's risk control measures. Here are my other logs. I found in the logs that at 2024/09/03 - 11:05:14, WhatsApp was in a CONNECTED state and ready to execute the next sending task. However, immediately after that, for some unknown reason, the page was reloaded, and after the reload, __checkQrCode need_scan=True. After that, all operations became meaningless.
|
try
|
this log from start wpp or after time ? |
This log was generated a few days later. |
In fact, the basic status is CONNECTED, but the network may not necessarily be connected, which seems to lack reference value.
|
I believe the issue I am encountering is similar to the one described here: |
Actually, I also suspect it might be a device configuration issue: wppconnect-team/wppconnect#1462 (comment) |
|
for now, no clear reason |
The WPP_Whatsapp module cannot be sent after running continuously for a period of time. I don't know what the reason is.
The text was updated successfully, but these errors were encountered: