Closed Rafamt16 closed 2 years ago
This is happening here too
Same error showing up
The same error here too!
1|Service1 | Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default') 1|Service1 | at puppeteer_evaluation_script:9:54 1|Service1 | at ExecutionContext._evaluateInternal (/www/wwwroot/whatsappv1/service1/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19) 1|Service1 | at processTicksAndRejections (internal/process/task_queues.js:95:5) 1|Service1 | at async ExecutionContext.evaluate (/www/wwwroot/whatsappv1/service1/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16) 1|Service1 | at async Client.initialize (/www/wwwroot/whatsappv1/service1/node_modules/whatsapp-web.js/src/Client.js:172:9)
npm update whatsapp-web.js
Hello, Does anyone know how to fix this error?
node:12216) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default') at puppeteer_evaluation_script:9:54 at ExecutionContext._evaluateInternal (C:\storm\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:\storm\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16) at async Client.initialize (C:\storm\node_modules\whatsapp-web.js\src\Client.js:172:9) (Use
node --trace-warnings ...
to show where the warning was created) (node:12216) 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: 1) (node:12216) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
@Rafamt16 Are you able to fix it?
Hi, I have similar problem:
(node:12684) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'AppState')
at __puppeteer_evaluation_script__:2:26
at ExecutionContext._evaluateInternal (C:\Users\whataspp-transfer\whatsapp-web-use\software\whatsapp-web-software\node_modules\whatsapp-web.js\node_modules\puppeteer\src\common\ExecutionContext.ts:273:13)
versions:
It happens when I use client.logout()
with authStrategy: LocalAuth
with specific dataPath
and clientId
.
Does anyone have idea why it is happening?
Hello, Does anyone know how to fix this error?
node:12216) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'default') at puppeteer_evaluation_script:9:54 at ExecutionContext._evaluateInternal (C:\storm\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:\storm\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16) at async Client.initialize (C:\storm\node_modules\whatsapp-web.js\src\Client.js:172:9) (Use
node --trace-warnings ...
to show where the warning was created) (node:12216) 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: 1) (node:12216) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.