[BUG] QR Code Generation Fails - Instances Stuck in Connecting Loop (v2.2.1)

[ikhaled-elazab]

Bug Description

Fresh WhatsApp instances fail to generate QR codes in Evolution API Lite v2.2.1. All new instances get stuck in an infinite "connecting" loop without ever generating QR codes.

Impact

• Cannot add new WhatsApp connections
• qrcode response always empty: {"count": 0}
• No QRCODE_UPDATED webhook events triggered
• Makes Baileys integration unusable for new instances

Root Cause

Auth state providers (use-multi-file-auth-state-*.ts) pre-initialize credentials using initAuthCreds() before Baileys connects. This causes Baileys to treat all connections as reconnection attempts instead of fresh connections requiring QR codes.

Key Files:

• src/utils/use-multi-file-auth-state-prisma.ts:130-134
• src/utils/use-multi-file-auth-state-redis-db.ts:39
• src/utils/use-multi-file-auth-state-provider-files.ts:89

Reproduction Steps

1. Create fresh instance: POST /instance/create with "qrcode": true
2. Instance status shows "connecting"
3. No QR code is generated (count stays at 0)
4. Instance loops reconnecting indefinitely

Proposed Solution

Modify auth providers to NOT pre-initialize credentials for fresh instances. Only initialize credentials after QR code scan completes.

[bientavu]

Hi @shw2ypro I had the exact same issue on my side and passing CONFIG_SESSION_PHONE_VERSION="" fixed it. I figured out this variable was injected via .env.example in the Dockerfile. As it is an outdated version I guess whatsapp just rejects it.