Ready event never fires after authentication (v1.34.6, WhatsApp Web 2.3000.x)

[danpasecinic]

Is there an existing issue for this?

• I have searched the existing issues.

Is this a problem caused by your code, or is it specifically because of the library?

• I have double-checked my code carefully.

Describe the bug.

After scanning the QR code, the authenticated event fires (three times), but the ready event never fires. The client gets stuck and never becomes usable.

[INFO] Initializing WhatsApp client...
[INFO] Scan this QR code with WhatsApp:
[QR code displayed]
[INFO] WhatsApp authenticated
[INFO] WhatsApp authenticated
[INFO] WhatsApp authenticated
// ready never fires, client is stuck

I've checked relevant issues, and the fixes suggested there did NOT help.

Expected Behavior

After authenticated, the ready event should fire and the client should become usable.

Steps to Reproduce the Bug or Issue

1. Install whatsapp-web.js v1.34.6 from npm, or some custom branches such as github:DouglasReisofc/whatsapp-web.js#fix/events-ready-messages or github:timothydillan/whatsapp-web.js#fix/ready-event-not-firing.
2. Initialize client with remote webVersionCache pointing to latest wa-version
3. Scan QR code
4. Observe: authenticated fires 3 times, ready never fires

WhatsApp Account Type

Standard

Browser Type

Chromium

Operation System Type

Amazon Linux 2 (EC2), Docker

WhatsApp-Web.js Version

1.34.6

WhatsApp Web Version

2.3000.1034260505-alpha

Node.js Version

24

Authentication Strategy

LocalAuth

Additional Context

No response

[alexandrejr-rajtecnologia]

Estou com o mesmo problema!!!

[Noninus]

same here

[BenyFilho]

1- Don't use WebCacheVersion;
2- Delete folder node_modules, .wwebjs_auth and .wwebjs_cache
3- install latest commits on main branch: npm install github:pedroslopez/whatsapp-web.js#main
4- Start your bot

[danpasecinic]

Appreciate you, @BenyFilho.

[danpasecinic]

For anyone running in Docker, one extra thing: if you were using system Chromium (apt-get install chromium + PUPPETEER_EXECUTABLE_PATH), you'll want to let Puppeteer download its own bundled Chrome instead. The system Chromium (v144) was causing the ready event to hang, while Puppeteer's bundled Chrome (v145) works fine.

[felmarv]

Hit this on two production bots (whatsapp-web.js 1.34.7, LocalAuth). Symptom: after a process restart, authenticated fires but ready never does — loading_screen reaches 100%, then silence. A fresh pairing always reaches ready; only session RESTORE hangs. Started 2026-06-20 when WhatsApp rolled out web build 2.3000.1041842691.

What did NOT work: installing #main; pinning webVersionCache to the latest 2.3000.x; clearing .wwebjs_cache. (The recent 2.3000.1041xxx builds carry the bug.)

What FIXED it: pin webVersion to an older, pre-breakage build, served from a local cache:

const client = new Client({
  authStrategy: new LocalAuth(),
  webVersion: '2.3000.1037753511-alpha',
  webVersionCache: { type: 'local', path: '/path/to/cache' }, // holds 2.3000.1037753511-alpha.html
});

Download the HTML once from wppconnect-team/wa-version to <path>/<version>.html. Use type: 'local', not remote — wa-version prunes old builds, so a remote pin to an old version 404s and you hang again; the local file is immune.

Validation: survived 5+ consecutive restarts (restore → ready in ~3s each) on two bots + scheduled 8h restarts. Pick a build from a few days before your symptom appeared.

Related: #5717, #5758, #127085.

[scrawner]

@felmarv could you solve this?
I'm having a similar issue

In my case, loading reaches 100% then stops without firing ready event.
Sometimes, loading starts from 0%, reaches 100% then ready event fires (usually when a message is received).
I noticed that when sync happens, ready event fires (new message, stories, etc)

I am using whatsapp-web.js 1.34.7, LocalAuth

I opened this issue 201821 but maybe I can solve with your solution
I also posted an error in a try catch I tested here in the Client.js

Hope you have something
thanks