[WEBJS] - WAHA fails after WhatsApp Web update – Error: "No LID for user" + "window.Store.ContactMethods.getIsMyContact is not a function"

[danirpa]

After the most recent WhatsApp Web update (version 2025.11.x), the WAHA container stopped being able to send messages through /api/sendText.
Even though the session authenticates correctly and WAHA reports "session:default is ready", every attempt to send a message results in:
Error: No LID for user
TypeError: window.Store.ContactMethods.getIsMyContact is not a function
This indicates a breaking change in WhatsApp Web's internal API (window.Store), affecting the WebJS engine used by WAHA.

This issue occurred after WhatsApp Web updated (the logs show: "version":"2025.11.3").

"message":"No LID for user"

TypeError: window.Store.ContactMethods.getIsMyContact is not a function

and references to new minified WhatsApp Web JS files: https://static.whatsapp.net/rsrc.php/v4/yu/...
This indicates the WhatsApp Web internal API changed and broke the WebJS patches.

This is a compatibility break caused by a recent WhatsApp Web update.
WAHA/WebJS is still calling functions that no longer exist:
window.Store.ContactMethods.getIsMyContact

[FranciscoMateusVG]

Yep, im facing the same issue on my windows machine

[devlikepro]

could you try 2025.11.4 🤞

[danirpa]

o WAHA ainda não está funcionando após a atualização. O erro que recebemos é o mesmo de antes:

500 Internal Server Error com a mensagem "No LID for user".

O erro indica claramente que:

O WhatsApp Web está na versão 2025.11.4.

O WAHA (WebJS engine) está falhando ao carregar o LID (Local Identifier), um componente essencial da autenticação Multi-Dispositivo, devido à incompatibilidade de código.

[github-actions]

English

---

WAHA is still not working after updating. The error we receive is the same as before:

500 Internal Server Error with the message "No LID for user".

The error clearly indicates that:

WhatsApp Web is at version 2025.11.4.

WAHA (WebJS engine) is failing to load the LID (Local Identifier), an essential component of Multi-Device authentication, due to code incompatibility.

[devlikepro]

Could you check the phone number using
https://waha.devlike.pro/docs/how-to/contacts/#check-phone-number-exists
and
https://waha.devlike.pro/docs/how-to/contacts/#get-lid-by-phone-number

[danirpa]

O WhatsApp Web (v2025.11.4) mudou, e o WAHA (WebJS) não consegue mais encontrar o identificador de dispositivo (LID) necessário para iniciar a comunicação.

Mensagem de Erro: "No LID for user".

O problema é que o WAHA não consegue sequer iniciar o processo de comunicação devido à quebra de compatibilidade. O endpoint check-exists só funciona depois que o WAHA está totalmente funcional e conectado à API interna do WhatsApp.

Se o WAHA não consegue estabelecer a sessão com o LID, ele não pode realizar nenhuma ação, nem mesmo verificar a existência de um número.

[github-actions]

English

---

WhatsApp Web (v2025.11.4) has changed, and WAHA (WebJS) can no longer find the device identifier (LID) required to initiate communication.

Error Message: "No LID for user".

The problem is that WAHA cannot even start the communication process due to broken compatibility. The check-exists endpoint only works after WAHA is fully functional and connected to WhatsApp's internal API.

If WAHA cannot establish the session with the LID, it cannot perform any action, not even check for the existence of a number.

[lcava000]

WhatsApp’s introduction of the new LID identifier is causing significant issues for WAHA users, forcing many to quickly adjust their implementation rules.
I have a few questions to better understand the situation:

Does the LID change over time, or is it a static identifier assigned to each user?
Why do some sessions still work with @c.us while others only work with @lid? What determines this behavior?
Will it still be possible to send messages to contacts that are not saved in the address book?

Finally, is it technically feasible for WAHA to include an internal mechanism that automatically resolves the correct LID, while still allowing developers to send messages using the traditional @c.us format in the sendText API?

[ramonperetti]

Hey guys!

While i debugging for discover which contacts contains this problem i noticed what some contacts has presented @lid in chatId (after version update from 9 to 12) therefore don't freeze @xxx in your ambient