#issue with webpack-exodus version

17 messages Β· Page 1 of 1 (latest)

formal mulch
#

Hi!
Lately, I've been unable to connect to WhatsApp using whatsapp-web.js.
I read this discussion in this PR: https://github.com/pedroslopez/whatsapp-web.js/pull/2816

I understand that I need to use the new webpack-exodus version.

So, I did the following:

  • Deleted the wwebjs_auth directory
  • Installed the new version with: npm i github:pedroslopez/whatsapp-web.js#webpack-exodus
  • Stopped using the webVersionCache property
    Now, my configuration looks like this:
    {
    authStrategy: new LocalAuth({
    clientId: "" ,
    dataPath: "" ,
    }),
    puppeteer: {
    executablePath: "" ,
    }
    }

However, I still can't log in. I see the QR code, but the loading event never ends.

GitHub

TL;DR:
WhatsApp released 2.3000x, a version that does not use Webpack anymore. We had to change the Store system to no longer use moduleRaid. Instability issues are caused by relying on selectors &...

#

I get the following error:

(node:8096) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of null (reading '1')
at LocalWebCache.persist (C:\Users\a\resources\app.asar\node_modules\whatsapp-web.js\src\webCache\LocalWebCache.js:34:69)
at C:\Users\a\resources\app.asar\node_modules\whatsapp-web.js\src\Client.js:744:36
at processTicksAndRejections (node:internal/process/task_queues:95:5)
(Use WhatsappTransfer --trace-warnings ... to show where the warning was created)
(node:8096) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
init account failed Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default')
at puppeteer_evaluation_script:5:95
at ExecutionContext._evaluateInternal (C:\Users\a\resources\app.asar\node_modules\whatsapp-web.js\node_modules\puppeteer\src\common\ExecutionContext.ts:273:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at ExecutionContext.evaluate (C:\Users\a\resources\app.asar\node_modules\whatsapp-web.js\node_modules\puppeteer\src\common\ExecutionContext.ts:140:12)
at WhatsappClient.initialize (C:\Users\a\resources\app.asar\node_modules\whatsapp-web.js\src\Client.js:323:9)

Has anyone else encountered this issue and resolved it? Does anyone know why this might be happening? I would greatly appreciate any assistance!
Thanks!

vernal gate
#

you got rid of the executablePath for puppeteer? Please add the proper path to your chome / chromium executable or get rid of this part of configuration.

Same for LocalAuth config, provide a proper sessionId and data path or use default settings by getting rid of both settings.

formal mulch
#

I changed everything so now the confirmation looks like this: {authStrategy: new LocalAuth()} but It throw the same errors

#

I deleted also the wwebjs_auth folder

plucky spire
formal mulch
#

I removed the node_modules

#

There is a way to be sure that the package I am using is the exodus version?

formal mulch
#

So now I did those steps:

  • I removed again the node_modules
  • make sure that the package.json contains the GitHub path to exodus version
  • run npm install
  • change the configuration to be like that:
    {
    authStrategy: new LocalAuth({
    dataPath: uuidv4(),
    }),
    }
    (So now there is no way it will use any cache)
  • run the program

But the results was the same and it throw the same errors

#

Do you have idea why it is happening?

cerulean vessel
#

maybe you can try this code in your client :

restartOnAuthFail: true,
puppeteer: {
headless: true,
args: [
'--no-sandbox',
'--disable-setuid-sandbox',
'--disable-dev-shm-usage',
'--disable-accelerated-2d-canvas',
'--no-first-run',
'--no-zygote',
'--single-process', // <-- this one doesn't works in Windows
'--disable-gpu'
]
},

plucky spire
silver totem
#

Need more info

#

i'd remove the uuidv4 datapath its too long for a folder name and looks like it will create a new one every time

Hosting on a server? and what country is server located

+what country is your phone number

To receive help, provide:

  1. Whatsapp-web.js lib version πŸ“š
  2. Whatsapp web version (client.getWwebVersion()) 🌐,
  3. Using cache? ("none"/"local"/"remote") πŸ—„οΈ
  4. Connecting business or normal account 🏒,
  5. Using Chrome or chromium 🌍,
  6. Send the part of the code relevant to the error, if there is an error send an image of the error πŸ“Έ.
silver totem
#

or better send your package-lock.json