Regarding the Multi-device BETA. (CLICK HERE) #758

PurpShell · 2021-07-14T20:43:23Z

I opened this issue to discuss the multi-device beta that just got announced and available to everyone at the latest version of the WhatsApp and WhatsApp Business beta.

We are in the final stages of supporting this beta update, and we need your help. Visit #889 to help test.

ps: pinned because of so many issues

PurpShell · 2021-07-14T20:51:58Z

localStorage

{
  "history-sync-earliest-date": "1618517463",
  "md-opted-in": "true",
  "WARoutingInfo": "{\"domain\":\"fb\",\"edgeRouting\":\"CA0IBQ==\"}",
  "f86SIKHSKlIRpTDW+hsAiQ==": "{\"id\":\"global_mute\",\"expiration\":0}",
  "4P/5geRSELQs6BOP78jHJA==": "{\"DELETE_MSG_CLEAR_MEDIA\":true,\"MD_PAYMENT\":true,\"ARCHIVE_BROADCAST\":true,\"RECENT_EMOJI_SYNC\":true,\"VOIP_VOICE_CALL\":true,\"DESKTOP_VOIP_VOICE_CALL\":true,\"DESKTOP_VOIP_VIDEO_CALL\":true,\"MD_BACKEND\":true,\"MD_ADV\":true,\"MD_VOIP_GROUP\":false,\"VOIP_INDIVIDUAL_OUTGOING\":true,\"GROUPS_V_3\":true,\"GROUPS_V_3_CREATE\":false,\"CHANGE_NUMBER_V_2\":true,\"QUERY_STATUS_V_3_THUMBNAIL\":false,\"LIVE_LOCATIONS\":true,\"QUERY_VNAME\":true,\"VOIP_INDIVIDUAL_INCOMING\":true,\"PAYMENTS\":true,\"STICKER_PACK_QUERY\":true,\"LIVE_LOCATIONS_FINAL\":true,\"MEDIA_UPLOAD\":true,\"VNAME_V_2\":true,\"VIDEO_PLAYBACK_URL\":true,\"STATUS_RANKING\":true,\"VOIP_INDIVIDUAL_VIDEO\":false,\"THIRD_PARTY_STICKERS\":true,\"FREQUENTLY_FORWARDED_SETTING\":true,\"GROUPS_V_4_JOIN_PERMISSION\":true,\"RECENT_STICKERS\":false,\"CATALOG\":true,\"STARRED_STICKERS\":false,\"TEMPLATE_MESSAGE\":true,\"TEMPLATE_MESSAGE_INTERACTIVITY\":false,\"EPHEMERAL_MESSAGES\":true,\"RECENT_STICKERS_V_2\":true,\"USER_NOTICE\":true,\"SUPPORT\":true,\"GROUP_UII_CLEANUP\":true}",
  "DmSuwvU7JZflIEQn2wbPRg==": "\"{\\\"9618xxxx95-1624479435@g.us\\\":\\\"1:QENIbvzu\\\",\\\"x96xxxxxxx8-162xxxxxx6@g.us\\\":\\\"1:yeFyj1P5\\\"}\"",
  "Ha6V0naB+Asaj7QK9E9Yhw==": "false",
  "jytAU/x5IFaodumGFgGCqQ==": "false",
  "remember-me": "true",
  "WaInitialHistorySynced": "\"true\"",
  "Q9l1pa9U6RusJLJ/OGoVmw==": "{\"readReceipts\":\"all\",\"groupAdd\":\"all\",\"profilePicture\":\"all\",\"about\":\"all\",\"lastSeen\":\"all\"}",
  "dX8DofUHWjwPKlwiKhrvbg==": "false",
  "MdUpgradeWamFlag": "false",
  "WebEncKeySalt": "\"akzrRxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxUkv9Q=\"",
  "last-wid-md": "\"xxxxxxxx2x8:2@c.us\"",
  "WALogPreemptiveCleanUp": "false",
  "DcsZisUDFOGXo22KiEczVw==": "true",
  "WAHistorySyncStatus": "{\"initialCompleted\":true,\"recentCompleted\":true}",
  "MdHistoryLastChunkProcessed": "\"3_1\"",
  "syncd_disabled_due_to_fatal": "false",
  "WANoiseInfoIv": "[\"exxfxxxxxxxYDxxxxQ==\",\"mxxTx7Kxxxxxx3x5xxxA==\",\"exxxxxx/+36Fxxxxxg==\"]",
  "critical_data_synced": "true",
  "nSsarI/MAjXIC+UZpEdYEQ==": "[0,17]",
  "7qZ3zUZ0x8WTp6gYa0npDg==": "\"{}\"",
  "WANoiseInfo": "{\"recoveryToken\":\"B82GoA6DzVxxxxxxRJtzYk5gM=\",\"pubKey\":\"6umXxxxxxxxxxxxxxxINxDxxRkxxxxxxxxTvsxb\",\"privKey\":\"ZLxxxxxxLxxFZynAxxxxxxxxxxPvEpqExxxxxmK\"}",
  "pBzk5ZV/gj4KEC8gIJo2WA==": "\"SJKJLDKSJLD\"",
  "lFi24bP/zxekbO3AVtNXXA==": "[]",
  "abprops": "{\"hash\":\"1Xv5L1\",\"lastSyncTime\":1626293473539}",
  "debugCursor": "1196",
  "WALangPref": "\"en\"",
  "dpKjR53BUeu6nmFjKBsnaQ==": "{\"FavC7xOxxxxxxQ==\":1}",
  "contact-sync-refresh-seconds": "527917",
  "WAShouldCheckContactSyncStatus": "true",
  "mobile-platform": "\"android\"",
  "whatsapp-mutex": "\"x813505889:init_1626295122038\"",
  "WABrowserId": "\"RYc8V8xxxxxxxxx7WwuEg==\""
}

PurpShell · 2021-07-14T22:21:50Z

Seems the main hurdle is the selector we wait for:

Before:

After:

PurpShell · 2021-07-14T22:39:12Z

SUCCESS!

PurpShell · 2021-07-14T22:39:47Z

PurpShell · 2021-07-14T22:45:26Z

hmm, this was about Store and mR

the only hurdle i can see is the session

PurpShell · 2021-07-14T23:31:28Z

using session is proving pretty hard, seems they are using the IndexedDB;

before:

after:

PurpShell · 2021-07-14T23:42:44Z

able to import the database, now trying to set it.

PurpShell · 2021-07-15T00:06:09Z

Hey! I would like to know how you guys would like me to handle this. I am going to open a Pull request to just get the bare minimum out there, regarding sessions, i have a few puzzling questions to ask, hopefully you guys can answer!

Would it be better if the library had control over where it places it's session and database files? As an example:
you specify: something like infoPath: "./wweb-info/"in the ClientOptions and the library would go: ./wweb-info/ID/indexedDB/signal-storage.json. (YES/no), provide your way of solving this if you find it an issue!
How do you guys close your node app? (CTRL+C, restart via nodemon etc.) and would you rather have a (timed interval between saves (ClientOption; saveIntervalMs: 20000), save on detect of closing the app, or both just in case)

PurpShell · 2021-07-15T00:53:29Z

#761 has been opened. I'll add my experimental systems there.

Darker935 · 2021-07-15T01:22:52Z

Hey! I would like to know how you guys would like me to handle this. I am going to open a Pull request to just get the bare minimum out there, regarding sessions, i have a few puzzling questions to ask, hopefully you guys can answer!

Would it be better if the library had control over where it places it's session and database files? As an example:
you specify: something like infoPath: "./wweb-info/"in the ClientOptions and the library would go: ./wweb-info/ID/indexedDB/signal-storage.json. (YES/no), provide your way of solving this if you find it an issue!

How do you guys close your node app? (CTRL+C, restart via nodemon etc.) and would you rather have a (timed interval between saves (ClientOption; saveIntervalMs: 20), save on detect of closing the app, or both just in case)

Have a default path, controlled by lib, but we can change the path

I close with CTRL + C, or pm2 delete process_pid

PurpShell · 2021-07-15T01:45:28Z

Hey! I would like to know how you guys would like me to handle this. I am going to open a Pull request to just get the bare minimum out there, regarding sessions, i have a few puzzling questions to ask, hopefully you guys can answer!

Would it be better if the library had control over where it places it's session and database files? As an example:
you specify: something like infoPath: "./wweb-info/"in the ClientOptions and the library would go: ./wweb-info/ID/indexedDB/signal-storage.json. (YES/no), provide your way of solving this if you find it an issue!

How do you guys close your node app? (CTRL+C, restart via nodemon etc.) and would you rather have a (timed interval between saves (ClientOption; saveIntervalMs: 20), save on detect of closing the app, or both just in case)

Have a default path, controlled by lib, but we can change the path

I close with CTRL + C, or pm2 delete process_pid

the path is based on operating system? I think that path should be placed by the user

PurpShell · 2021-07-15T01:52:45Z

Hey! I would like to know how you guys would like me to handle this. I am going to open a Pull request to just get the bare minimum out there, regarding sessions, i have a few puzzling questions to ask, hopefully you guys can answer!

Would it be better if the library had control over where it places it's session and database files? As an example:
you specify: something like infoPath: "./wweb-info/"in the ClientOptions and the library would go: ./wweb-info/ID/indexedDB/signal-storage.json. (YES/no), provide your way of solving this if you find it an issue!

How do you guys close your node app? (CTRL+C, restart via nodemon etc.) and would you rather have a (timed interval between saves (ClientOption; saveIntervalMs: 20000), save on detect of closing the app, or both just in case)

@pedroslopez I would like your thoughts!

PurpShell · 2021-07-15T01:56:05Z

I know for a fact some people store data in databases, so I don't know how i'll support it for them.. Maybe a "exportAll.json" where the structure would be like this:

{
  localStorage: {},
  indexedDB: {}
}

pedroslopez · 2021-07-15T02:15:17Z

Super interesting! Thanks for looking into this.

From what I'm understanding, WhatsApp Web when in multi-device mode no longer stores any information in localStorage and instead stores everything (including session information) in IndexedDB, so our current solution of injecting the session into localStorage before loading WhatsApp Web no longer works, is that correct?

Puppeteer has a built-in way of persisting these things by specifying a userDataDir path, which includes persisting IndexedDB as well as localStorage. However, I'd like to avoid requiring the use of the local filesystem since people might be running things in a container, which doesn't have a persistent filesystem at least by default. To this point, the session.json that we're writing today as part of examples is just one way of doing it, and people are free to load the session keys from a database or wherever else they need. I would like to keep this functionality if possible.

I think a potential path forward is to see what are the minimal values we need to persist to be able to start up a whatsapp session. This probably contains no past message data, but only things required for authentication. Then, we could do something similar to what we do for localStorage and have a pre-step that writes these things to IndexedDB instead as needed.

PurpShell · 2021-07-15T12:36:19Z

Super interesting! Thanks for looking into this.

From what I'm understanding, WhatsApp Web when in multi-device mode no longer stores any information in localStorage and instead stores everything (including session information) in IndexedDB, so our current solution of injecting the session into localStorage before loading WhatsApp Web no longer works, is that correct?

Puppeteer has a built-in way of persisting these things by specifying a userDataDir path, which includes persisting IndexedDB as well as localStorage. However, I'd like to avoid requiring the use of the local filesystem since people might be running things in a container, which doesn't have a persistent filesystem at least by default. To this point, the session.json that we're writing today as part of examples is just one way of doing it, and people are free to load the session keys from a database or wherever else they need. I would like to keep this functionality if possible.

I think a potential path forward is to see what are the minimal values we need to persist to be able to start up a whatsapp session. This probably contains no past message data, but only things required for authentication. Then, we could do something similar to what we do for localStorage and have a pre-step that writes these things to IndexedDB instead as needed.

yes, it results in a no internet error, and some metadata in localStorage is required like keys, etc..
i searched yesterday, and I found userDataDir. Though it seemed it'll contain too much junk, and it is unprepared for multiple instances, and as you said, people with containers and restarting servers that reset the file-system to it's original state.
I found the minimal values of localStorage, i'll see what happens if i remove the database of chats, contacts, messages

olirock · 2021-07-21T02:29:31Z

any update? :/

PurpShell · 2021-07-23T10:15:29Z

Super interesting! Thanks for looking into this.
From what I'm understanding, WhatsApp Web when in multi-device mode no longer stores any information in localStorage and instead stores everything (including session information) in IndexedDB, so our current solution of injecting the session into localStorage before loading WhatsApp Web no longer works, is that correct?
Puppeteer has a built-in way of persisting these things by specifying a userDataDir path, which includes persisting IndexedDB as well as localStorage. However, I'd like to avoid requiring the use of the local filesystem since people might be running things in a container, which doesn't have a persistent filesystem at least by default. To this point, the session.json that we're writing today as part of examples is just one way of doing it, and people are free to load the session keys from a database or wherever else they need. I would like to keep this functionality if possible.
I think a potential path forward is to see what are the minimal values we need to persist to be able to start up a whatsapp session. This probably contains no past message data, but only things required for authentication. Then, we could do something similar to what we do for localStorage and have a pre-step that writes these things to IndexedDB instead as needed.

yes, it results in a no internet error, and some metadata in localStorage is required like keys, etc..

i searched yesterday, and I found userDataDir. Though it seemed it'll contain too much junk, and it is unprepared for multiple instances, and as you said, people with containers and restarting servers that reset the file-system to it's original state.

I found the minimal values of localStorage, i'll see what happens if i remove the database of chats, contacts, messages

I'm implementing a file management system, debating on userDataDir since it also saves data of other open tabs in the browser aswell. I am going for an Observer with a custom system to save the indexedDB now.

I'm also going to push that to #761, so stay tuned for later today as i'll talk about it on the WWebJS discord.

thewh1teagle · 2021-08-06T23:06:23Z

@PurpShell
Hi
to store credentials all you need to do is to backup & restore signal-storage, wawc, wawc_db_enc databases inside indexeddb + localStorage (that's not a lot of data)
now, the challenge after you restore the session is to re-trigger re-sync of chats, messages, etc... has happen once when you log in.
otherwise when you restore the session you will not get your chat history.

PurpShell · 2021-08-13T18:23:30Z

@PurpShell
Hi
to store credentials all you need to do is to backup & restore signal-storage, wawc, wawc_db_enc databases inside indexeddb + localStorage (that's not a lot of data)
now, the challenge after you restore the session is to re-trigger re-sync of chats, messages, etc... has happen once when you log in.
otherwise when you restore the session you will not get your chat history.

Hey! I've already documented what you said above. I am working on & testing a file management system solution. I have worked out some stuff that can potentially trigger a re-sync, looks promising.

PurpShell · 2021-08-13T18:25:05Z

After a bunch of days of inactivity, whatsapp re-syncs with the phone. This is shown in a "Downloading Messages X%" message on the splash screen. So far, I've found webpack methods that can re-trigger synchronization.

IKallS · 2021-12-23T13:11:55Z

Hi! Does anybody successfully restore session in Beta?

yes I did, I just create a session by requiring the json file for a saved session and then create a new client with this session data https://guide.wwebjs.dev/features/resuming-sessions

It didn't work for me. The script creates the session but does not remain after restart

`const fs = require('fs');
const axios = require('axios');
const { Client, Location } = require('./index');
const SESSION_FILE_PATH = './session.json';
let sessionCfg;

if (fs.existsSync(SESSION_FILE_PATH)) {
sessionCfg = require(SESSION_FILE_PATH);
}

const client = new Client({
puppeteer: {
headless: false,
// executablePath: "node_modules/puppeteer/.local-chromium/win64-901912/chrome-win/chrome", // chromium default path
executablePath: "/Program Files/Google/Chrome/Application/chrome",
}, session: sessionCfg
});

client.on('authenticated', (session) => {
console.log('AUTHENTICATED', session);
sessionCfg=session;
fs.writeFile(SESSION_FILE_PATH, JSON.stringify(session), function (err) {
if (err) {
console.error(err);
}
});
});`

mahmouds12 · 2022-01-04T22:08:02Z

Hi! Does anybody successfully restore session in Beta?

yes I did, I just create a session by requiring the json file for a saved session and then create a new client with this session data https://guide.wwebjs.dev/features/resuming-sessions

It didn't work for me. The script creates the session but does not remain after restart

`const fs = require('fs'); const axios = require('axios'); const { Client, Location } = require('./index'); const SESSION_FILE_PATH = './session.json'; let sessionCfg;

if (fs.existsSync(SESSION_FILE_PATH)) { sessionCfg = require(SESSION_FILE_PATH); }

const client = new Client({ puppeteer: { headless: false, // executablePath: "node_modules/puppeteer/.local-chromium/win64-901912/chrome-win/chrome", // chromium default path executablePath: "/Program Files/Google/Chrome/Application/chrome", }, session: sessionCfg });

client.on('authenticated', (session) => { console.log('AUTHENTICATED', session); sessionCfg=session; fs.writeFile(SESSION_FILE_PATH, JSON.stringify(session), function (err) { if (err) { console.error(err); } }); });`

It used to work in Oct-Nov, but now when I tried again it doesn't seem to work.
In previous versions of whatsapp-web.js MD Beta, it used to automatically store a file called "wweb.json" inside folder "/WWebJS/session-{sessionName}/wweb.json", I used to restore session using this json file, but now this wweb.json is not created and I can't even create it manually as it's always undefined in MD.

mahmouds12 · 2022-01-04T22:43:36Z

Hi! Does anybody successfully restore session in Beta?

yes I did, I just create a session by requiring the json file for a saved session and then create a new client with this session data https://guide.wwebjs.dev/features/resuming-sessions

It didn't work for me. The script creates the session but does not remain after restart
const fs = require('fs'); const axios = require('axios'); const { Client, Location } = require('./index'); const SESSION_FILE_PATH = './session.json'; let sessionCfg; if (fs.existsSync(SESSION_FILE_PATH)) { sessionCfg = require(SESSION_FILE_PATH); } const client = new Client({ puppeteer: { headless: false, // executablePath: "node_modules/puppeteer/.local-chromium/win64-901912/chrome-win/chrome", // chromium default path executablePath: "/Program Files/Google/Chrome/Application/chrome", }, session: sessionCfg }); client.on('authenticated', (session) => { console.log('AUTHENTICATED', session); sessionCfg=session; fs.writeFile(SESSION_FILE_PATH, JSON.stringify(session), function (err) { if (err) { console.error(err); } }); });

It used to work in Oct-Nov, but now when I tried again it doesn't seem to work. In previous versions of whatsapp-web.js MD Beta, it used to automatically store a file called "wweb.json" inside folder "/WWebJS/session-{sessionName}/wweb.json", I used to restore session using this json file, but now this wweb.json is not created and I can't even create it manually as it's always undefined in MD.

Actually it works with me in a different approach now... I read the directories inside WWebJS folder and loop through each subfolder (each subfolder is a session folder) and then create a new client with clientId same as the folder name without the word "session-", and it restores the session automatically
here's the code:

const { readdirSync }=require('fs')

const getDirectories=(source) => {

    return readdirSync(source, { withFileTypes: true })
        .filter(dirent => dirent.isDirectory())
        .map(dirent => dirent.name)
}
const currentDir=__dirname + '\\WWebJS\\';
const dirArray=getDirectories(currentDir);

dirArray.forEach(async (element) => {
    if (element==="session") return;
    const sessionName=element.replace("session-", "");
    try {
        global.client[sessionName]=new Client({
            puppeteer: {
                headless: true,
                args: ['--no-sandbox']
            },
            clientId: sessionName,
        });
    } catch (error) {
        console.log(sessionName + ' error while initiating New Client!');
    }

    global.client[sessionName].on('ready', () => {
        console.log(sessionName + ' Client is ready!');
    });
    global.client[sessionName].initialize();

});

zaidanprtm · 2022-01-07T03:59:14Z

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'serialize')
at __puppeteer_evaluation_script__:12:24
at ExecutionContext._evaluateInternal (/project/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ExecutionContext.evaluate (/project/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16)
at async Client.sendMessage (/project/whatsapp/node_modules/whatsapp-web.js/src/Client.js:572:28)
at async Client.<anonymous> (/project/whatsapp/whatsapp-multidevice.js:193:5)

Hi, I got this error after i rescanning qr and try to send a reply message. Any idea how to solve it? Thanks a lot

zaidanprtm · 2022-01-07T07:34:25Z

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'serialize')
at __puppeteer_evaluation_script__:12:24
at ExecutionContext._evaluateInternal (/project/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ExecutionContext.evaluate (/project/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16)
at async Client.sendMessage (/project/whatsapp/node_modules/whatsapp-web.js/src/Client.js:572:28)
at async Client.<anonymous> (/project/whatsapp/whatsapp-multidevice.js:193:5)

Hi, I got this error after i rescanning qr and try to send a reply message. Any idea how to solve it? Thanks a lot

UPDATE: fixed by reinstalling using npm i github:pedroslopez/whatsapp-web.js#multidevice

krishzuz · 2022-01-08T15:21:50Z

Is there any way to track the initialization process like after scanning the QR code it takes some time to download the data right can we track that timing (eg: loading)

excalibur1010 · 2022-01-24T23:43:17Z

`D:\wabot3\node_modules\whatsapp-web.js\src\Client.js:452
async destroy() {
^^^^^^^

SyntaxError: Unexpected identifier
←[90m at Object.compileFunction (node:vm:352:18)←[39m
←[90m at wrapSafe (node:internal/modules/cjs/loader:1031:15)←[39m
←[90m at Module._compile (node:internal/modules/cjs/loader:1065:27)←[39m
←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)←[39m
←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m
←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m
←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m
←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m
at Object. (D:\wabot3\node_modules\←[4mwhatsapp-web.js←[24m\index.js:6:13)
←[90m at Module._compile (node:internal/modules/cjs/loader:1101:14)←[39m
`

Hi, I got this error after update

sistemas-y-redes · 2022-01-25T11:56:34Z

`D:\wabot3\node_modules\whatsapp-web.js\src\Client.js:452 async destroy() { ^^^^^^^

SyntaxError: Unexpected identifier ←[90m at Object.compileFunction (node:vm:352:18)←[39m ←[90m at wrapSafe (node:internal/modules/cjs/loader:1031:15)←[39m ←[90m at Module._compile (node:internal/modules/cjs/loader:1065:27)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object. (D:\wabot3\node_modules\←[4mwhatsapp-web.js←[24m\index.js:6:13) ←[90m at Module._compile (node:internal/modules/cjs/loader:1101:14)←[39m `

Hi, I got this error after update

I am getting this same error, other files are also giving syntax errors

sistemas-y-redes · 2022-01-26T08:09:41Z

D:\wabot3\node_modules\whatsapp-web.js\src\Client.js:452 async destroy() { ^^^^^^^ SyntaxError: Unexpected identifier ←[90m at Object.compileFunction (node:vm:352:18)←[39m ←[90m at wrapSafe (node:internal/modules/cjs/loader:1031:15)←[39m ←[90m at Module._compile (node:internal/modules/cjs/loader:1065:27)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object. (D:\wabot3\node_modules\←[4mwhatsapp-web.js←[24m\index.js:6:13) ←[90m at Module._compile (node:internal/modules/cjs/loader:1101:14)←[39m
Hi, I got this error after update

I am getting this same error, other files are also giving syntax errors

This happens with the latest version, I have had another bot running in an older version and this morning it errors with this message:

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'Sticker')
at puppeteer_evaluation_script:32:70

sistemas-y-redes · 2022-01-27T08:39:08Z

I have switched to node version 17.2.0 and now it works.
Please make it compatible with 12.4.0

casaservice · 2022-01-27T09:23:08Z

I have switched to node version 17.2.0 and now it works. Please make it compatible with 12.4.0

hello sistemas-y-redes you still using the same packages whatsapp-web.js or the new one : npm i github:pedroslopez/whatsapp-web.js#multidevice

please answer i have the same probleme

sistemas-y-redes · 2022-01-27T09:52:17Z

I have switched to node version 17.2.0 and now it works. Please make it compatible with 12.4.0

hello sistemas-y-redes you still using the same packages whatsapp-web.js or the new one : npm i github:pedroslopez/whatsapp-web.js#multidevice

please answer i have the same probleme

I am using the multidevice branch

jeremyandes · 2022-01-28T00:11:56Z

Hi everyone!

I'm trying to reply with buttons in multidevice, but the message is never delivered, it's working but only with string messages.

My code is something like this:

let button = new Buttons(
    `Hi! Welcome to initial config of ${NameApp}`,
    [
        { body: '• Button example 1' },
        { body: '• Button example 2' },
        { body: '• Button example 3' },
    ],
    `Hi ${name}!`,
    footer,
);
client.sendMessage(msg.from, button);

And my client is this one:

const client = new Client({
    puppeteer: {
        headless: false,
        args: [
            '--no-sandbox',
        ],
        clientId: 'example',
        disableMessageHistory: true 
    }
});

Any thoughts?

voxsoftware · 2022-01-28T00:13:57Z

In WhatsApp FAQ clearly says in multidevice some functions like button no works. El jue., 27 de enero de 2022 7:12 p. m., Jeremy Andes < ***@***.***> escribió:

…

Hi everyone! I'm trying to reply with buttons in multidevice, but the message is never delivered, it's working but only with string messages. My code is something like this: let button = new Buttons( `Hi! Welcome to initial config of ${NameApp}`, [ { body: '• Button example 1' }, { body: '• Button example 2' }, { body: '• Button example 3' }, ], `Hi ${name}!`, footer, ); client.sendMessage(msg.from, button); And my client is this one: const client = new Client({ puppeteer: { headless: false, args: [ '--no-sandbox', ], clientId: 'example', disableMessageHistory: true } }); Any thoughts? — Reply to this email directly, view it on GitHub <#758 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADT6M7DLPMCLJSCNHVOVCFDUYHNNXANCNFSM5AMGHTCA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

jeremyandes · 2022-01-28T00:16:06Z

Thank you @voxsoftware for your quick answer!

setsmart · 2022-02-20T22:29:59Z

hello all,

Install via npm i github:pedroslopez/whatsapp-web.js#multidevice

this is part of this update:

Multi-device branch #889

error message that appears after executing the above command:

code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\Users\set_t\OneDrive\Área de Trabalho\WhatsApp-Buttons\whatsapp-web.js-main\src\Client.js',
'C:\Users\set_t\OneDrive\Área de Trabalho\WhatsApp-Buttons\whatsapp-web.js-main\index.js',
'C:\Users\set_t\OneDrive\Área de Trabalho\WhatsApp-Buttons\whatsapp-web.js-main\example.js'
]
}

NowDev · 2022-02-25T16:08:19Z

I've noticed that multidevice isn't a beta feature anymore and i don't even have the option to disable it.

elhumbertoz · 2022-02-25T21:17:44Z

Error after scan QR.

(node:23136) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'Socket') at __puppeteer_evaluation_script__:6:62 at ExecutionContext._evaluateInternal (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19) at processTicksAndRejections (internal/process/task_queues.js:95:5) at async ExecutionContext.evaluate (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16) at async Client.initialize (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\src\Client.js:227:9)

elhumbertoz · 2022-02-25T21:39:43Z

Error after scan QR.

(node:23136) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'Socket') at __puppeteer_evaluation_script__:6:62 at ExecutionContext._evaluateInternal (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19) at processTicksAndRejections (internal/process/task_queues.js:95:5) at async ExecutionContext.evaluate (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16) at async Client.initialize (C:\Dropbox\CEO.source\mywhatsapp\node_modules\whatsapp-web.js\src\Client.js:227:9)

Resolved in: https://github.com/pedroslopez/whatsapp-web.js/pull/889/files/358bb9d0a83f54d4fccabc8634943d97a9a8318f..25c66acf0def4f0296ebe9c917d6855eaa2f859c

LittleKing205 · 2022-02-26T01:40:00Z

I've noticed that multidevice isn't a beta feature anymore and i don't even have the option to disable it.

Me too... What I have to Do now?

pedroslopez · 2022-02-26T02:19:22Z

@NowDev @LittleKing205 and everyone else that's now stuck not being able to use main:

If you really really can't wait, you can use the multidevice branch directly by following the instructions on #889
HOWEVER, at this point I would suggest against it because I'm aiming to get multidevice support on main and released this weekend, and there will be a couple changes in the MD branch vs what will end up going on main.

LittleKing205 · 2022-02-26T02:41:41Z

I can wait for it. You make a realy great job with this package. I was a little bit irritated today, that my bot gas stopped ther work.

pedroslopez · 2022-02-28T04:27:53Z

Multi-device support is now released as part of v1.16.0. Thanks everyone for testing!

Check out the release notes at https://github.com/pedroslopez/whatsapp-web.js/releases/tag/v1.16.0

PortalAt12345 · 2022-03-02T22:51:08Z

Dear Pedroslopez, first of all I really really appreciate your effort and hard work. I want to all you about my scenario, I use a Dual App when I trying to connect (QR SCAN) it shows error on terminal 'Multi device can not connected' something like that kindly fix this issue. once again respect for your effort.👏👏👏
Peace

jeremyandes · 2022-03-02T23:28:56Z

@PortalAt12345 this issue is closed due to multidevice support in main branch.

Btw you can take a look to what auth-strategy is the best for you: https://wwebjs.dev/guide/authentication.html

PortalAt12345 · 2022-03-03T19:52:56Z

@PortalAt12345 this issue is closed due to multidevice support in main branch.

Btw you can take a look to what auth-strategy is the best for you: https://wwebjs.dev/guide/authentication.html

No, it is for multi-device this solution not meet my scenario. my scenario is different, I used multi accounts (clone apps) with the help of this app I can use more than one WhatsApp account in same phone in simple words, I have 3 different WhatsApp in same phone with different number. It shows an error
Scanning Device Config:

App Name: Multiple Accounts
Phone Name: Xiaomi Note 11
Android Version: 11

PurpShell added enhancement New feature or request whatsapp change A change has occurred in WhatsApp Web that breaks functionality labels Jul 14, 2021

This comment has been minimized.

Sign in to view

Ryuk-me mentioned this issue Jul 21, 2021

Can't start client with multidevice beta #794

Closed

PurpShell linked a pull request Jul 23, 2021 that will close this issue

Multi-device Support [TESTERS NEEDED!] #761

Closed

5 tasks

k4m4r82 mentioned this issue Aug 5, 2021

Update WhatsApp BETA WhatsAppNETClient/WhatsAppNETClient2#2

Closed

PurpShell mentioned this issue Aug 13, 2021

wa BETA #835

Closed

This was referenced Aug 20, 2021

Multi-Device Link [Whatsapp Beta] #842

Closed

Multi-device Support [TESTERS NEEDED!] #761

Closed

PurpShell mentioned this issue Sep 5, 2021

whatsapp-web beta not working. #863

Closed

fdciabdul mentioned this issue Jan 24, 2022

UnhandledPromiseRejectionWarning: Error: Multi-device is not yet supported by whatsapp-web.js. Please check out https://github.com/pedroslopez/whatsapp-web.js/pull/889 to follow the progress. #1120

Closed

guicuton mentioned this issue Feb 25, 2022

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'Socket') #1242

Closed

pedroslopez closed this as completed Feb 28, 2022

pedroslopez unpinned this issue Mar 2, 2022

Regarding the Multi-device BETA. (CLICK HERE) #758

Regarding the Multi-device BETA. (CLICK HERE) #758

Comments

PurpShell commented Jul 14, 2021 • edited Loading

PurpShell commented Jul 14, 2021 • edited Loading

PurpShell commented Jul 14, 2021

This comment has been minimized.

PurpShell commented Jul 14, 2021

PurpShell commented Jul 14, 2021

PurpShell commented Jul 14, 2021

PurpShell commented Jul 14, 2021

PurpShell commented Jul 14, 2021

PurpShell commented Jul 15, 2021 • edited Loading

PurpShell commented Jul 15, 2021

Darker935 commented Jul 15, 2021

PurpShell commented Jul 15, 2021

PurpShell commented Jul 15, 2021

PurpShell commented Jul 15, 2021

pedroslopez commented Jul 15, 2021 • edited Loading

PurpShell commented Jul 15, 2021 • edited Loading

olirock commented Jul 21, 2021

PurpShell commented Jul 23, 2021

thewh1teagle commented Aug 6, 2021

PurpShell commented Aug 13, 2021

PurpShell commented Aug 13, 2021 • edited Loading

IKallS commented Dec 23, 2021

mahmouds12 commented Jan 4, 2022 • edited Loading

mahmouds12 commented Jan 4, 2022 • edited Loading

zaidanprtm commented Jan 7, 2022 • edited Loading

zaidanprtm commented Jan 7, 2022

krishzuz commented Jan 8, 2022

excalibur1010 commented Jan 24, 2022

sistemas-y-redes commented Jan 25, 2022

sistemas-y-redes commented Jan 26, 2022

sistemas-y-redes commented Jan 27, 2022

casaservice commented Jan 27, 2022

sistemas-y-redes commented Jan 27, 2022

jeremyandes commented Jan 28, 2022

voxsoftware commented Jan 28, 2022 via email

jeremyandes commented Jan 28, 2022

setsmart commented Feb 20, 2022 • edited Loading

NowDev commented Feb 25, 2022

elhumbertoz commented Feb 25, 2022

elhumbertoz commented Feb 25, 2022

LittleKing205 commented Feb 26, 2022

pedroslopez commented Feb 26, 2022

LittleKing205 commented Feb 26, 2022 • edited Loading

pedroslopez commented Feb 28, 2022

PortalAt12345 commented Mar 2, 2022

jeremyandes commented Mar 2, 2022 • edited Loading

PortalAt12345 commented Mar 3, 2022

PurpShell commented Jul 14, 2021 •

edited

Loading

PurpShell commented Jul 14, 2021 •

edited

Loading

PurpShell commented Jul 15, 2021 •

edited

Loading

pedroslopez commented Jul 15, 2021 •

edited

Loading

PurpShell commented Jul 15, 2021 •

edited

Loading

PurpShell commented Aug 13, 2021 •

edited

Loading

mahmouds12 commented Jan 4, 2022 •

edited

Loading

mahmouds12 commented Jan 4, 2022 •

edited

Loading

zaidanprtm commented Jan 7, 2022 •

edited

Loading

setsmart commented Feb 20, 2022 •

edited

Loading

LittleKing205 commented Feb 26, 2022 •

edited

Loading

jeremyandes commented Mar 2, 2022 •

edited

Loading