On 'ready' is not fired #2458

TheMacros · 2023-08-29T15:29:59Z

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

I'm trying to create a very basic app that handles incoming messages from WhatsApp.

The code generates a QR code successfully, but when I scan it with WhatsApp (link device) with an iOS or Android app nothing happens.
The QR code is scanned successfully and the linked device (browser) appears on my mobile device.
However, in the console, I didn't receive 'Client is ready!' message or any other message (like 'Client is authenticated!' or 'Client is auth_failure!') - absolutely nothing. When I disconnect the device I also don't receive the message 'Client is disconnected!'.
Also, I have no exceptions.

Expected behavior

I'm expecting the on('ready') should fire when I scan the QR code and on('disconnected') should be fired when device is removed

Steps to Reproduce the Bug or Issue

There are no steps to reproduce.

Relevant Code

import waweb from "whatsapp-web.js";
import qrcode from 'qrcode-terminal';

const { Client, LocalAuth } = waweb;

const client = new Client({
    puppeteer: {
        args: [
            '--no-sandbox',
            '--disable-setuid-sandbox'
        ],
    }
});

client.on('qr', qr => {
    qrcode.generate(qr, {small: true});
});

client.on('ready', () => {
    console.log('Client is ready!');
});

client.on('disconnected', () => {
    console.log('Client is disconnected!');
});

client.on('authenticated', () => {
    console.log('Client is authenticated!');
});

client.on('auth_failure', () => {
    console.log('Client is auth_failure!');
});

client.initialize();

Browser Type

Chromium

WhatsApp Account Type

Standard

Does your WhatsApp account have multidevice enabled?

Yes, I am using Multi Device

Environment

OS: Ubuntu Linux 18.04
Phone: iOS or Android
whatsapp-web.js: 1.22.1
WhatsApp Web version: 2.2335.9
Node: 16.15.1

Additional context

I have another app (that uses whatsapp-web) running on the same server. It works fine.

The text was updated successfully, but these errors were encountered:

TheMacros · 2023-08-29T16:21:05Z

Just tested the same script with the same version (1.22.1) on macOS - the same result.
If I run it with puppeteer.headless = false on macOS - I see that the authorization process is working in Chromium (so in the Chromium browser I see my account authorized), but still nothing I can see in the script output.

I've also tried the 1.22.2-alpha.0 - this version works fine! So I'll stay on the alpha for now.
But the question is how the 1.22.1 is working on my other project.

frnndwrms · 2023-08-29T17:39:15Z

same here with latest version El mar, 29 ago 2023 a la(s) 13:21, TheMacros ***@***.***) escribió:

…

Just tested the same script with the same version (1.22.1) on macOS - the same result. If I run it with *puppeteer.headless = false* on macOS - I see that the authorization process is working in Chromium (so in the Chromium browser I see my account authorized), but still nothing I can see in the script output. I've also tried the 1.22.2-alpha.0 - this version works fine! So I'll stay on the alpha for now. But the question is how the 1.22.1 is working on my other project. — Reply to this email directly, view it on GitHub <#2458 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOQBBZJSBX6WN5YXQ3UP7DTXXYJJXANCNFSM6AAAAAA4DESGSE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Fernando Wermus. Los contenidos de este mensaje, y los archivos adjuntos, son de carácter confidencial. Si ud. no es el legitimo destinatario de este mensaje, avise inmediatamente al remitente y borre este mensaje. Cualquier distribución o divulgación no autorizada de este mensaje y sus archivos asociados está prohibida. Por favor infórmenos inmediatamente y destruya el original o cualquier impresión del mismo. Important Note: This e-mail (including any attachments) is confidential and intended only for the use of the addressee (s) named herein. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original e-mail and any printouts.

AndersonVale · 2023-08-29T19:49:07Z

same here. version 1.22.1

MatheusOliveira-dev · 2023-08-29T21:18:34Z

Did changing this file fix the problem for you? It worked for me: fix

pecintamantan · 2023-08-30T07:03:27Z

same here i think my vps is broken but not :v

neckell · 2023-08-30T19:05:21Z

same here. I tried on Linux (WSL) using docker and localhost, worked fine. But on production (azure) somehow it's not working 1.22.1 version. And it started happing just before updating from stable 1.21.0 version

YagoRosa · 2023-08-30T21:52:11Z

Same here on chrome.

MarlonRibeirodeMelo · 2023-08-30T21:54:42Z

I have the same problem, using ubuntu 18, it stopped working completely

rogerthedeveloper · 2023-08-30T22:25:10Z

Me too, the same behavior here, when expecting the ready event to be fired

neckell · 2023-08-30T22:40:18Z

1.22.2-alpha.0 works fine

yan043 · 2023-08-31T01:43:58Z

it's working for me in version 1.22.1

EpicJosch · 2023-08-31T09:25:27Z

same error

EpicJosch · 2023-08-31T09:27:59Z

Did changing this file fix the problem for you? It worked for me: fix

thanks man! this really fixes the issue!

dev-dfBueno · 2023-08-31T12:53:40Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

ItzFerr · 2023-08-31T13:46:06Z

same here, it solved when i changed to 1.22.2-alpha.0

dev-dfBueno · 2023-08-31T15:12:40Z

mesmo aqui, resolveu quando mudei para 1.22.2-alpha.0

Como que muda?
Pode me ajudar?

EdnaldoTaurino · 2023-08-31T19:18:45Z

tbm quero saber como muda

max-programming · 2023-08-31T20:24:41Z

Did changing this file fix the problem for you? It worked for me: fix

Thanks!
But I got this new error

max-programming · 2023-08-31T20:25:21Z

Also @ItzFerr I got this error when switching to the alpha

thiagootero · 2023-08-31T20:53:10Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

Replace in src/Client.js

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';

to

const INTRO_IMG_SELECTOR = "[data-icon='chat']"

thiagootero · 2023-08-31T20:54:04Z

tbm quero saber como muda

Altere o arquivo package.json, alterando a versão do whatsapp web. Depois, rode o comando npm install

areumtecnologia · 2023-09-01T17:56:11Z

npm i whatsapp-web.js@1.22.2-alpha.0 --save

YagoRosa · 2023-09-01T21:05:19Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

Replace in src/Client.js

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';

to

const INTRO_IMG_SELECTOR = "[data-icon='chat']"

I updated to version whatsapp-web.js@1.22.2-alpha.0

I changed the code :

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light ="true"], [data-asset-intro-image-dark="true"]';

for

const INTRO_IMG_SELECTOR = '[data-icon='chat']';

It still didn't work, and now the QR code doesn't even appear for me to scan with my cell phone.

does anyone have any suggestions?

I'll keep looking to see if I find a solution.

andresmv94 · 2023-09-01T21:16:33Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

Replace in src/Client.js
const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';
to
const INTRO_IMG_SELECTOR = "[data-icon='chat']"

I updated to version whatsapp-web.js@1.22.2-alpha.0

I changed the code :

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light ="true"], [data-asset-intro-image-dark="true"]';

for

const INTRO_IMG_SELECTOR = '[data-icon='chat']';

It still didn't work, and now the QR code doesn't even appear for me to scan with my cell phone.

does anyone have any suggestions?

I'll keep looking to see if I find a solution.

same here

YagoRosa · 2023-09-02T13:16:33Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

Replace in src/Client.js
const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';
to
const INTRO_IMG_SELECTOR = "[data-icon='chat']"

I updated to version whatsapp-web.js@1.22.2-alpha.0

I changed the code :

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light ="true"], [data-asset-intro-image-dark="true"]';

for

const INTRO_IMG_SELECTOR = '[data-icon='chat']';

It still didn't work, and now the QR code doesn't even appear for me to scan with my cell phone.

does anyone have any suggestions?

I'll keep looking to see if I find a solution.

Alright, in issue #2439 I found a comment from @joulgs about uninstalling whatsapp-web.js

npm unistall whatsapp-web.js -S

and then add it to the package.json file in the dependencies

"whatsapp-web.js": "https://github.com/Julzk/whatsapp-web.js/tarball/jkr_hotfix_8"

After changing just run the code

npm install

the client came back, it shows that whatsapp was connected but it gives an error

Error: Evaluation failed: Error: wid error: invalid wid

/workspaces/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221
throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));

does anyone have any suggestions?

I will keep looking for a solution.

YagoRosa · 2023-09-02T17:40:58Z

Alterar este arquivo resolveu o problema para você? Funcionou para mim: consertar

Pra mim não rolou não :'(

Replace in src/Client.js
const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';
to
const INTRO_IMG_SELECTOR = "[data-icon='chat']"

I updated to version whatsapp-web.js@1.22.2-alpha.0
I changed the code :
const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light ="true"], [data-asset-intro-image-dark="true"]';
for
const INTRO_IMG_SELECTOR = '[data-icon='chat']';
It still didn't work, and now the QR code doesn't even appear for me to scan with my cell phone.
does anyone have any suggestions?
I'll keep looking to see if I find a solution.

Alright, in issue #2439 I found a comment from @joulgs about uninstalling whatsapp-web.js

npm unistall whatsapp-web.js -S

and then add it to the package.json file in the dependencies

"whatsapp-web.js": "https://github.com/Julzk/whatsapp-web.js/tarball/jkr_hotfix_8"

After changing just run the code

npm install

the client came back, it shows that whatsapp was connected but it gives an error

Error: Evaluation failed: Error: wid error: invalid wid

/workspaces/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221 throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));

does anyone have any suggestions?

I will keep looking for a solution.

I don't know what could have happened but apparently the authenticator was causing some conflict.

With me I used the following code for authentication :

const { Client, LocalAuth } = require('whatsapp-web.js');
const client = new Client({
authStrategy: new LocalAuth()
});

I changed to :

const { Client } = require('whatsapp-web.js');
const client = new Client();

Now it's working perfectly, I don't know what could have caused the bug that was happening to me but when I removed the authenticator it started working normally again, all messages are being sent and the bot responds perfectly.

granaber · 2023-09-02T21:21:01Z

This soluction is change to version alpha, 1.22.1 Not working !

SonuSubhadip · 2023-09-05T05:12:13Z

1st
npm uninstall whatsapp-web.js
2nd
npm install whatsapp-web.js
3rd
Goto > node_modules > whatsapp-web.js > src > client.js > Replace
const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light="true"], [data-asset-intro-image-dark="true"]';
With
const INTRO_IMG_SELECTOR = "[data-icon='chat']";
Enjoy ❤️

dev-dfBueno · 2023-09-05T10:50:13Z

Alterar este arquivo resolveu o problema para você? Função para mim: devolver

Pra mim não rolou não :'(

Substitua em src/Client.js

const INTRO_IMG_SELECTOR = '[data-testid="intro-md-beta-logo-dark"], [data-testid="intro-md-beta-logo-light"], [data-asset-intro-image-light ="true"], [data-asset-intro-image-dark="true"]';

pára

const INTRO_IMG_SELECTOR = "[data-icon='chat']"

Aqui resolveu, alterei dessa forma e alterei também o package pra Alpha.. Obrigado!!

almacres10 · 2023-09-07T04:52:22Z

i still havent found the solution for this, i have try to change the script in Client.js and still the client ready doesnt show up. I have updated the package to whatsapp-web.js 1.22.2-alpha.0 and still doesnt worked. Any other solution?

almacres10 · 2023-09-07T04:52:33Z

i still havent found the solution for this, i have try to change the script in Client.js and still the client ready doesnt show up. I have updated the package to whatsapp-web.js 1.22.2-alpha.0 and still doesnt worked. Any other solution?

neckell · 2023-09-07T05:04:38Z

i still havent found the solution for this, i have try to change the script in Client.js and still the client ready doesnt show up. I have updated the package to whatsapp-web.js 1.22.2-alpha.0 and still doesnt worked. Any other solution?

You should either implement the fix the guys found out on this issue or wait for the release of a new patch version.
For implementing the fix, you need to fork the repo and create a new one.

For instance, I will leave here my repo with the corresponding bugfix (working) in case any other want it until stable release come out: https://github.com/neckell/whatsapp-web.js
This repo contains whatsapp-web.js@1.22.2-alpha.0 + the ready fix
You can temporarily change your package json as follows:

"whatsapp-web.js": "github:neckell/whatsapp-web.js",

leodutra · 2023-09-11T00:33:45Z

This fix worked for me #2485

burakerenel · 2023-09-20T07:08:31Z

This fix worked for me #2485

mine too

fpiantoni · 2023-09-28T22:23:28Z

The error is still happening, the new fix is:
const INTRO_IMG_SELECTOR = '[data-icon='new-chat']';

On the Client.js file from the Package

neckell · 2023-09-28T22:32:54Z

@fpiantoni did you check on the repo i quoted? I am not quite sure about new-chat, i tested it and didn't work for me

fpiantoni · 2023-09-28T22:35:08Z

@neckell let me check it. I just found that in another reponse, tested it and worked. Let me pull your package and test it.
I will keep you updated

neckell · 2023-09-28T22:37:39Z

I added a new state "Synced" that's fired when a syncronization between mobile phone and instance is complete. It's not official, it's up for my needs

LucasMonteiroi · 2023-10-04T19:20:30Z

This works for me, just updated the package version, this is my sample code:

const qrcode = require('qrcode-terminal');
const { Client, LocalAuth } = require('whatsapp-web.js');

const client = new Client({
  puppeteer: {
    args: ['--no-sandbox', '--disable-setuid-sandbox'],
  },
});

client.on('qr', (qr) => {
  qrcode.generate(qr, { small: true });
});

client.on('ready', () => {
  console.log('Client is ready!');
});

client.on('disconnected', () => {
  console.log('Client is disconnected!');
});

client.on('authenticated', () => {
  console.log('Client is authenticated!');
});

client.on('auth_failure', () => {
  console.log('Client is auth_failure!');
});

client.on('message', (msg) => {
  if (msg.body == '!ping') {
    msg.reply('pong');
  }
});

client.initialize();

learntheropes · 2023-12-02T04:44:31Z

@alechkos which is the commit of this fix?

alechkos · 2023-12-02T04:50:46Z

@learntheropes

npm i github:pedroslopez/whatsapp-web.js#main

learntheropes · 2023-12-02T04:55:53Z

@alechkos yes, but I can't find how this has been fixed on the repo.

TheMacros added the bug Something isn't working label Aug 29, 2023

alechkos closed this as completed Dec 2, 2023

Repository owner locked and limited conversation to collaborators Dec 2, 2023

On 'ready' is not fired #2458

On 'ready' is not fired #2458

Comments

TheMacros commented Aug 29, 2023 • edited Loading

Is there an existing issue for this?

Describe the bug

Expected behavior

Steps to Reproduce the Bug or Issue

Relevant Code

Browser Type

WhatsApp Account Type

Does your WhatsApp account have multidevice enabled?

Environment

Additional context

TheMacros commented Aug 29, 2023

frnndwrms commented Aug 29, 2023 via email

AndersonVale commented Aug 29, 2023

MatheusOliveira-dev commented Aug 29, 2023

pecintamantan commented Aug 30, 2023 • edited Loading

neckell commented Aug 30, 2023

YagoRosa commented Aug 30, 2023

MarlonRibeirodeMelo commented Aug 30, 2023

rogerthedeveloper commented Aug 30, 2023

neckell commented Aug 30, 2023

yan043 commented Aug 31, 2023

EpicJosch commented Aug 31, 2023

EpicJosch commented Aug 31, 2023

dev-dfBueno commented Aug 31, 2023

ItzFerr commented Aug 31, 2023

dev-dfBueno commented Aug 31, 2023

EdnaldoTaurino commented Aug 31, 2023

max-programming commented Aug 31, 2023

max-programming commented Aug 31, 2023 • edited Loading

thiagootero commented Aug 31, 2023

thiagootero commented Aug 31, 2023

areumtecnologia commented Sep 1, 2023

YagoRosa commented Sep 1, 2023

andresmv94 commented Sep 1, 2023

YagoRosa commented Sep 2, 2023

YagoRosa commented Sep 2, 2023

granaber commented Sep 2, 2023

SonuSubhadip commented Sep 5, 2023 • edited Loading

dev-dfBueno commented Sep 5, 2023

almacres10 commented Sep 7, 2023

almacres10 commented Sep 7, 2023

neckell commented Sep 7, 2023 • edited Loading

leodutra commented Sep 11, 2023

burakerenel commented Sep 20, 2023

fpiantoni commented Sep 28, 2023

neckell commented Sep 28, 2023 • edited Loading

fpiantoni commented Sep 28, 2023

neckell commented Sep 28, 2023 • edited Loading

LucasMonteiroi commented Oct 4, 2023

learntheropes commented Dec 2, 2023

alechkos commented Dec 2, 2023

learntheropes commented Dec 2, 2023

TheMacros commented Aug 29, 2023 •

edited

Loading

pecintamantan commented Aug 30, 2023 •

edited

Loading

max-programming commented Aug 31, 2023 •

edited

Loading

SonuSubhadip commented Sep 5, 2023 •

edited

Loading

neckell commented Sep 7, 2023 •

edited

Loading

neckell commented Sep 28, 2023 •

edited

Loading

neckell commented Sep 28, 2023 •

edited

Loading