Error: No LID for user

[developeralphaebarcode]

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.

viHqVFvzl0J.js:77 Uncaught (in promise) Error: No LID for user
at i (viHqVFvzl0J.js:77:180)
at Object.b [as toUserLidOrThrow] (J9mfDF-2dez.js:50:941)
at Object. (xzSLf8qiA7U.js:1436:1138)
at Generator.next ()
at h (viHqVFvzl0J.js:151:125)
at g (viHqVFvzl0J.js:151:349)
at viHqVFvzl0J.js:151:408
at new Promise ()
at Object. (viHqVFvzl0J.js:151:277)
at Object.t [as findOrCreateLatestChat] (xzSLf8qiA7U.js:1436:713)
at window.WWebJS.getChat (VM41 about:blank:959:57)

Expected Behavior

no error

Steps to Reproduce the Bug or Issue

send message

WhatsApp Account Type

WhatsApp Business

Browser Type

Chromium

Operation System Type

Windows

Phone OS Type

Android

WhatsApp-Web.js Version

1.34.1

WhatsApp Web Version

Version 2.3000.1027526765

Node.js Version

v22.18.0

Authentication Strategy

LocalAuth

Additional Context

No response

[adamzayn101]

Please check this number use this wa.me/whatsapp_number from
1- the Puppeteer window after start your project "whatsapp-web.js" &
2- from Official WhatsApp Web ...

Does it open a chat window with the number, or does it show as an invalid number?

[developeralphaebarcode]

Yes It's showing invalid number in both Puppeteer window and Official WhatsApp Web ... and in google chrome show error in console

Uncaught (in promise) Error: No LID for user
at i (nm6zFCzCNrS.js:77:180)
at Object.b [as toUserLidOrThrow] (7qS8RqOTSd-.js:50:941)
at Object. (XqzJjKAUldS.js:1435:1138)
at Generator.next ()
at h (nm6zFCzCNrS.js:151:125)
at g (nm6zFCzCNrS.js:151:349)
at nm6zFCzCNrS.js:151:408
at new Promise ()
at Object. (nm6zFCzCNrS.js:151:277)
at Object.t [as findOrCreateLatestChat] (XqzJjKAUldS.js:1435:713)
at Object. (b5JFjuJuQHV.js:202:5124)
at Generator.next ()
at h (nm6zFCzCNrS.js:151:125)
at g (nm6zFCzCNrS.js:151:349)
at nm6zFCzCNrS.js:151:408
at new Promise ()
at Object. (nm6zFCzCNrS.js:151:277)
at Object.current (b5JFjuJuQHV.js:202:5923)
at 1rcW6YHmT66yAQGqexb-mdkxmRfbSZJOQ9YJhdBlduHj7sh5Brkvxf_3PYDWazCdEXxFzncp9LOxOHqFx3B7PXG3bkGFxMGE9cjiDpO_ktt4ScmvIzcYHzY3tHaImj7R9kMxbEdyzp4vmolzMsd-Ug6elqKgDRyNq4h2s5dYO4soUymZjHq_GG9wtlMNtDOcR9Xx5kwXXqgH3vibFAAaUPnXb90mC1Ry3Ty0Yv3z3xli--D94jvsWqehdEtWw.js:1519:282
at co (hspnlwOy7Ir.js:11:166879)
at hspnlwOy7Ir.js:11:172296
at nm (hspnlwOy7Ir.js:11:152699)
at io (hspnlwOy7Ir.js:11:168345)
at kr (hspnlwOy7Ir.js:11:218461)
at ir (hspnlwOy7Ir.js:11:218283)
at HTMLDocument.f (hspnlwOy7Ir.js:11:167573)

[adamzayn101]

Just an idea. I haven't tried it because I don't have a number with any issues at the moment.

This code is located in src/util/Injected/Store.js:

window.injectToFunction({ module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' }, () => false);
On some devices, the session is disconnected after scanning the QR code #3811

And if deleting it (: The session is not disconnected, but this error occurs.

[seowzhenjun0126]

I am also facing the same issue, and it is caused by toUserLidOrThrow not returning any LID for the user I haven't contacted before.

This can be confirmed by running:

let wid = window.require('WAWebWidFactory').createUserWid("xxxxx@c.us");
await window.require("WAWebLidMigrationUtils").toUserLid(wid)

in the chrome dev console of WhatsApp web.

However, if I send a message to that manually to that contact in WhatsApp web and run the code above again, then LID is returned.

I also found a similar issue in wpp-connect (https://github.com/wppconnect-team/wa-js/pull/2842/files), but I'm not sure how they solve it. Does anyone has any idea?

[BenyFilho]

Guys, we will have to wait. Meta is changing it constantly. Today, the error is a bit clearer when you get a new number and try to get its LID
"lid-migrated client does not have an accountLid!"
It seems that not every number has an LID. It's as simple as that.

[seowzhenjun0126]

I am putting this down for someone who needs an urgent fix.

This codes forces the LID of a contact to be created by opening the chat => info side panel in the interface.

As far as I have tested this seems to be working but this is just a workaround and is not guarantee to work for every cases.

Replace the window.WWebJS.getChat function with this:

window.WWebJS.getChat = async (chatId, { getAsModel = true } = {}) => {
    const isChannel = /@\w*newsletter\b/.test(chatId);
    const chatWid = window.Store.WidFactory.createWid(chatId);

    let chat;

    if (isChannel) {
        try {
            chat = window.Store.NewsletterCollection.get(chatId);
            if (!chat) {
                await window.Store.ChannelUtils.loadNewsletterPreviewChat(chatId);
                chat = await window.Store.NewsletterCollection.find(chatWid);
            }
        } catch (err) {
            chat = null;
        }
    } else {
        chat = await window.Store.FindOrCreateChat.findOrCreateLatestChat(chatWid)
            .then(chat => chat.chat)
            .catch(async err => {
                chat = window.Store.Chat.get(chatWid) || (await window.Store.Chat.find(chatWid));
                if (!chat) {
                    return ;
                }

                try {
                    await window.Store.Cmd.openChatBottom(chat);
                    await window.Store.Cmd.openCurrentChatInfo();
                    await new Promise(resolve => setTimeout(resolve, 500));
                    await window.Store.Cmd.closeActiveChat();
                    chat = await window.Store.FindOrCreateChat.findOrCreateLatestChat(chatWid)
                } catch (err) {
                    return ;
                }
            })
    }

    return getAsModel && chat
        ? await window.WWebJS.getChatModel(chat, { isChannel: isChannel })
        : chat;
};

[adamzayn101]

@seowzhenjun0126 Thank you , it's work 100% With all the affected numbers.

But it's not a satisfactory solution... Opening the side panel in the interface
But it worked...and helps diagnose the problem.

[adamzayn101]

[FIX] Workaround for "No LID for user" error

I found a workaround that solved the No LID for user issue without having to open the chat info panel manually.
Basically I patched the internal WAWebLidMigrationUtils functions to gracefully fallback to the old WID when an accountLid is missing:

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' },
  () => false
);

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'shouldHaveAccountLid' },
  () => false
);

window.injectToFunction(
  { module: 'WAWebLidMigrationUtils', function: 'toUserLid' },
  (func, wid) => {
    try {
      return func(wid);
    } catch {
      return wid; // fallback to WID if conversion fails
    }
  }
);

@seowzhenjun0126
You can now try:

let wid = window.require('WAWebWidFactory').createUserWid("xxxxx@c.us");
await window.require("WAWebLidMigrationUtils").toUserLid(wid)

successfully after writing the above code in the Chrome Dev Console of WhatsApp Web.

Note : @BenyFilho
You need to resolve the error for this WAWebLid1X1MigrationGating injection
For the session disconnection issue after QR

[adamzayn101]

I resolved the session-disconnection issue by using a safer injection for injectToFunction.

I used :
window.injectToFunction({ module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' }, (func, ...args) => { try { return func(...args); } catch { return false; }});
instead of:
window.injectToFunction({ module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' }, () => false);

[BenyFilho]

[FIX] Workaround for "No LID for user" error

I found a workaround that solved the No LID for user issue without having to open the chat info panel manually. Basically I patched the internal WAWebLidMigrationUtils functions to gracefully fallback to the old WID when an accountLid is missing:

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' },
  () => false
);

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'shouldHaveAccountLid' },
  () => false
);

window.injectToFunction(
  { module: 'WAWebLidMigrationUtils', function: 'toUserLid' },
  (func, wid) => {
    try {
      return func(wid);
    } catch {
      return wid; // fallback to WID if conversion fails
    }
  }
);

Note : @BenyFilho You need to resolve the error for this WAWebLid1X1MigrationGating injection For the session disconnection issue after QR

Injecting this module is unsafe for many users. Meta double-checks and disconnects if the values ​​differ.

[BenyFilho]

I resolved the session-disconnection issue by using a safer injection for injectToFunction.

I used : window.injectToFunction({ module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' }, (func, ...args) => { try { return func(...args); } catch { return false; }}); instead of: window.injectToFunction({ module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' }, () => false);

Injecting this module is unsafe for many users. Meta double-checks and disconnects if the values ​​differ.

[adamzayn101]

@BenyFilho Thanks a lot for your notes 🙏

✅ A relatively safer way is not to override the function with a fixed () => false, but to wrap it with try/catch. That way the original logic still runs, and only if it throws an error we return the fallback:

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' },
  (func, ...args) => {
    try {
      return func(...args); // call original function
    } catch {
      return false; // fallback only if broken
    }
  }
);

What do you think?

[BenyFilho]

@BenyFilho Thanks a lot for your notes 🙏

✅ A relatively safer way is not to override the function with a fixed () => false, but to wrap it with try/catch. That way the original logic still runs, and only if it throws an error we return the fallback:

window.injectToFunction(
  { module: 'WAWebLid1X1MigrationGating', function: 'Lid1X1MigrationUtils.isLidMigrated' },
  (func, ...args) => {
    try {
      return func(...args); // call original function
    } catch {
      return false; // fallback only if broken
    }
  }
);

What do you think?

That's the problem, it never throws an error, so in theory, injecting that module that way is the same as doing nothing

[adamzayn101]

Another attempt to fix this was made with the numbers that showed the error "No LID for user", and it worked.

Replace the window.WWebJS.getChat function with this:

window.WWebJS.getChat = async (chatId, { getAsModel = true } = {}) => {
        const isChannel = /@\w*newsletter\b/.test(chatId);
        const chatWid = window.Store.WidFactory.createWid(chatId);

        let chat;

        if (isChannel) {
            try {
                chat = window.Store.NewsletterCollection.get(chatId);
                if (!chat) {
                    await window.Store.ChannelUtils.loadNewsletterPreviewChat(chatId);
                    chat = await window.Store.NewsletterCollection.find(chatWid);
                }
            } catch (err) {
                chat = null;
            }
        } else {
            chat = await window.Store.FindOrCreateChat.findOrCreateLatestChat(chatWid)
                .then(chat => chat.chat)
                .catch(async err => {

                  actions= [{
                        type: "add",
                        phoneNumber: chatWid.user
                      }]
                  let query = window.require("WAWebContactSyncUtils").constructUsyncDeltaQuery(actions);
                      let result =  await query.execute();
                  chat = window.Store.WidFactory.createWid(result.list[0].lid)
                   
                })
        }

        return getAsModel && chat
            ? await window.WWebJS.getChatModel(chat, { isChannel: isChannel })
            : chat;
    };