Please fix 🙏
See original GitHub issueIs there an existing issue for this?
- I have searched the existing issues
Describe the bug
test
Expected behavior
test
Steps to Reproduce the Bug or Issue
test
Relevant Code
test
Browser Type
Chromium
WhatsApp Account Type
Standard
Does your WhatsApp account have multidevice enabled?
Yes, I am using Multi Device
Environment
(node:13056) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeErr
or: Cannot read properties of undefined (reading ‘default’)
at puppeteer_evaluation_script:14:123
at ExecutionContext._evaluateInternal (H:\Whatsapp 2022\Whatsapp Center\node
_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:221:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ExecutionContext.evaluate (H:\Whatsapp 2022\Whatsapp Center\node_mo
dules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:110:16)
at async Client.initialize (H:\Whatsapp 2022\Whatsapp Center\node_modules\wh
atsapp-web.js\src\Client.js:267:9)
(Use node --trace-warnings ...
to show where the warning was created)
(node:13056) 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 termin
ate the node process on unhandled promise rejection, use the CLI flag --unhandl ed-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti
ons_mode). (rejection id: 1)
(node:13056) [DEP0018] DeprecationWarning: Unhandled promise rejections are depr
ecated. In the future, promise rejections that are not handled will terminate th
e Node.js process with a non-zero exit code.
Additional context
No response
Issue Analytics
- State:
- Created 10 months ago
- Comments:13
@pedroslopez when this change will go live?
PR is in review bro -> https://github.com/pedroslopez/whatsapp-web.js/pull/1789