-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error ready QRCODE #16
Comments
need more details. |
@pranavms13 It happens to me as well. I am using OSX 11.1 with node v12.13.0 |
the same problem here. |
Same error. After scanning qr in /auth/getqr |
Nevermind...fixed by doing what @toni-ismail says on #23 |
I think this might also happen when someone deletes the token from WhatsApp. |
(node:5304) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read property 'default' of undefined
at puppeteer_evaluation_script:5:51
at ExecutionContext._evaluateInternal (C:\API03\whatsapp-node-api-master\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:217:19)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async ExecutionContext.evaluate (C:\API03\whatsapp-node-api-master\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:106:16)
at async Client.initialize (C:\API03\whatsapp-node-api-master\node_modules\whatsapp-web.js\src\Client.js:145:9)
(Use
node --trace-warnings ...
to show where the warning was created)(node:5304) 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:5304) [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.
The text was updated successfully, but these errors were encountered: