Skip to content
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 on sendText #309

Closed
brgomes opened this issue Nov 12, 2020 · 4 comments
Closed

Error on sendText #309

brgomes opened this issue Nov 12, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@brgomes
Copy link

brgomes commented Nov 12, 2020

(node:18049) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot convert undefined or null to object
at Function.assign ()
at Object.window.WAPI.getchatId (/home/bruno/www/estudos/whatsapp/node_modules/venom-bot/dist/lib/wapi/wapi.js:8:32278)
at async Object.window.WAPI.sendMessage (/home/bruno/www/estudos/whatsapp/node_modules/venom-bot/dist/lib/wapi/wapi.js:8:39096)
at ExecutionContext._evaluateInternal (/home/bruno/www/estudos/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ExecutionContext.evaluate (/home/bruno/www/estudos/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:106:16)
(Use node --trace-warnings ... to show where the warning was created)
(node:18049) 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:18049) [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.

@joaosouz4dev
Copy link
Contributor

whats version u are using?

@brgomes
Copy link
Author

brgomes commented Nov 12, 2020

Versão 2.0.18

@igortrust
Copy link

The same is happening here #306
I gave a bypass to avoid closing the venom.

(node:18049) UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot convert undefined or null to object
at Function.assign ()
at Object.window.WAPI.getchatId (/home/bruno/www/estudos/whatsapp/node_modules/venom-bot/dist/lib/wapi/wapi.js:8:32278)
at async Object.window.WAPI.sendMessage (/home/bruno/www/estudos/whatsapp/node_modules/venom-bot/dist/lib/wapi/wapi.js:8:39096)
at ExecutionContext._evaluateInternal (/home/bruno/www/estudos/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ExecutionContext.evaluate (/home/bruno/www/estudos/whatsapp/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:106:16)
(Use node --trace-warnings ... to show where the warning was created)
(node:18049) 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:18049) [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.

@edgardmessias edgardmessias added the bug Something isn't working label Nov 13, 2020
@joaosouz4dev
Copy link
Contributor

try using the new versions if the error persists please create an issue again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants