Cannot get qrcode event after restart.

hcfw007 commented 2 years ago

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug

When restart a whatsapp-web.js system without login and headless set to true, the system will stuck and no QR event will be triggered.

Expected behavior

Trigger QR event as starting a new session.

Steps to Reproduce the Bug or Issue

Steps to reproduce the problem:

set puppeteer.headless to true in example.js
start example.js and wait till qrcode appears.
terminate the system and restart.
system will stuck and no qrcode event will be triggered.

Relevant Code

Something might be helpful:

This might be realted to localAuth defined by whatsapp-web.js. If at first we start the system with headless as falsy, the problem will disappear. This hows that the localAuth generated by headless: off mode will prevent the problem.
However if we start with headless on but turn it off afterwards, the problem will remain. And the browswer will say that you need to update your Chrome to 60+ (actually we have 100.0.4889.0)
If we clear the localAuth folder, the problem will disappear.

Browser Type

Chromium

WhatsApp Account Type

Standard

Does your WhatsApp account have multidevice enabled?

Yes, I am using Multi Device

Environment

macOs 12.3.1 whatsapp-web.js 1.16.6 WhatsApp Web version 2.2216.8 Node.js 16.10.0

Additional context

No response

MinosIE commented 2 years ago

see https://github.com/pedroslopez/whatsapp-web.js/issues/1339 hope helpful

hcfw007 commented 2 years ago

see #1339 hope helpful

Unfortunately delete session every time is not acceptable for me here. Thanks anyway.

MinosIE commented 2 years ago

I get the same question again but diffrent is I meet it show up after scan code

glbatistabh commented 2 years ago

I'm also having the same problem and it started recently (the source code is the same and the problem didn't exist a few days ago. It was probably a WhstaApp Web change itself).

Notes:

Unfortunately, deleting the session directory is NOT an option for me.
Whatsapp-web.js version v1.16.6
WHATSAPP WEB version v2.2218.6
Yes, I am using Multi Device
Node version v16.15.0
Linux debian 10.12
Kernel 4.19.0-20-cloud-amd64 SMP Debian 4.19.235-1 (2022-03-17) x86_64 GNU/Linux
Browser Chromium AND Chorme (the error happens in 2 browsers)
WhatsApp Account Type Standard

xanaxxx commented 2 years ago

same issue here

MinosIE commented 2 years ago

This has not happened since I switched the stable agent

hcfw007 commented 2 years ago

solved after upgrading to latest version

xanaxxx commented 2 years ago

solved after upgrading to latest version

which command did you use?

hcfw007 commented 2 years ago

solved after upgrading to latest version

which command did you use?

Nothing, seems WhatsApp Web version v2.2220.8 does not contain such problem.

xanaxxx commented 2 years ago

solved after upgrading to latest version

which command did you use?

Nothing, seems WhatsApp Web version v2.2220.8 does not contain such problem.

if i use headless:true how can i see the version of my whatsapp and in that case how can update that?, if i dont use browser

hcfw007 commented 2 years ago

solved after upgrading to latest version

which command did you use?

Nothing, seems WhatsApp Web version v2.2220.8 does not contain such problem.

if i use headless:true how can i see the version of my whatsapp and in that case how can update that?, if i dont use browser

I think you don't have to do anything, just use the latest version of whatsapp-web.js.

GabrielFeMello commented 2 years ago

I'm using 1.17.1 and have no on('qr') being triggered by my client. I'm stucked. It started suddently. 2 days ago, the cliente trigerred a qr with a few inervals automatically.

LakmalHarshana commented 1 year ago

try using this package qrcode instead of qrcode-terminal. It worked for me

wernerpj1 commented 11 months ago

Can i connect without Qrcode in my opened browser with whatsweb logged?

pedroslopez / whatsapp-web.js