WhatsApp accounts requiring Passkey can no longer connect

[ArturGPJ]

Welcome!

• Yes, I have searched for similar requests on GitHub and found none.

What type of feature?

Integration

What is the motivation for the request?

One of my WhatsApp accounts has started requiring a Passkey to link new devices. There is no option to disable it.

When I try to connect through the official WhatsApp Web, after scanning the QR Code it requires creating/using a Passkey before completing the login.

However, with Evolution API (v2.4.0), after scanning the QR Code nothing happens. The Passkey prompt never appears, and after a while Evolution simply generates a new QR Code.

Logs:

connection: connecting
hasQr: true
qrcodeCount: 1

(scan QR Code)

...nothing happens...

hasQr: true
qrcodeCount: 2

It looks like WhatsApp is waiting for the new Passkey authentication flow, but Evolution/Baileys never reaches that step.

Environment

Evolution API: 2.4.0
WhatsApp: Latest version
Issue started only after this WhatsApp account began requiring Passkey.
Other WhatsApp accounts that do not require Passkey still connect normally.

Is this a known issue? Is there already support planned for the new Passkey authentication flow?

Usage Examples

No response

How should the feature be developed?

No response

Additional Notes

No response

[melissagobatti]

I’m experiencing the same issue here, but on Evolution API version 2.3.7.

After scanning the QR code, nothing happens, the passkey step never appears, and after some time a new QR code is generated again.

This started only for a WhatsApp account that now requires a passkey to link new devices. Other accounts that do not require a passkey are still connecting normally.

So it does not seem to be limited to version 2.4.0. It also affects 2.3.7 in my case.

[pontedigital1]

I am experiencing the same problem in version 2.3.7.

[dionathanbatista]

Estou enfrentando o mesmo problema

[AmineSamlali]

+1

[joaovitorlopes]

[PT-BR]
Eu consegui conectar meu WhatsApp Business somente no WhatsApp WEB, não deu no aplicativo e nem no evolutionapi, porém tive que fazer um malabarismo, tive que criar essa chave de acesso, ela vincula a conta google conectada no telefone, ai tive que logar essa conta google no Google Chrome (Só funciona no google Chrome), essa conta tem que estar como principal, ai ela para de pedir essa autenticação USB do Windows, e aparece a chave de segurança da conta, como se fosse um certificado digital, ai tem que definir uma senha (PIN), e depois ele pede até pra confirmar umas letras pra de fato acessar, ficou mais impossível de acessar o WhatsApp do que o aplicativo do banco. Enfim, tive que fazer tudo isso pra conseguir acessar o WhatsApp, não funciona no aplicativo, apenas no Web. E na evolution não se consegue resolver isso, será necessário uma grande atualização.
[EN]
I only managed to connect my WhatsApp Business account via WhatsApp Web; it didn't work on the app or with Evolution API. However, I had to jump through some hoops: I had to create an access key linked to the Google account on my phone, then log into that specific Google account in Google Chrome (it only works in Chrome). That account has to be set as the primary one; once that's done, it stops asking for Windows USB authentication and displays the account's security key—acting much like a digital certificate. Then you have to set a password (PIN), and it even asks you to confirm some characters to actually gain access. It’s become harder to access WhatsApp than my banking app. Anyway, I had to go through all that just to get into WhatsApp; it doesn't work on the app, only on the Web version. And there's no way to fix this within Evolution itself; a major update will be required.

[peteh]

Did you create a whatsapp username recently? For me it seems it started failing/requireing passkey after creating a user name.

[SamehElalfi]

Did you create a whatsapp username recently? For me it seems it started failing/requireing passkey after creating a user name.

Yes, I actually did create a WhatsApp username recently, and I'm seeing the exact same behavior. It started prompting for a passkey right after. Looks like a widespread bug with the new username rollout or a "security feature".

[joaovitorlopes]

Did you create a whatsapp username recently? For me it seems it started failing/requireing passkey after creating a user name.

I hadn't created the username yet when this problem occurred; it happened well after the option to reserve a username became available.

[dionathanbatista]

Nao usamos nome de usuario e mesmo assim pediu

[peteh]

Did you create a whatsapp username recently? For me it seems it started failing/requireing passkey after creating a user name.

I hadn't created the username yet when this problem occurred; it happened well after the option to reserve a username became available.

Then maybe it's just coincidence or depends on the whatsapp version.
Then we can ignore the theory that it's related.
On my old phone the account still works while I got signed out on my fairphone and require passkey now.

[kennedysmartins]

This starts to happening for me today too, I didn't setup any username
UP

[matheusmms031]

Same thing here, anyone have any ideas what to do?

[dionathanbatista]

Alguem ai com uma luz? suporte deles nem respondem.

[willianclic]

WhiskeySockets/Baileys#2672 (comment)
Tão no caminho...