orkestral / venom

Venom is a high-performance system developed with JavaScript to create a bot for WhatsApp, support for creating any interaction, such as customer service, media sending, sentence recognition based on artificial intelligence and all types of design architecture for WhatsApp.
https://orkestral.io
Apache License 2.0
6.07k stars 1.19k forks source link

Cant send or receive messages. #2102

Closed dgabriel2334 closed 1 year ago

dgabriel2334 commented 1 year ago

Description

Good morning friends. First I want to congratulate you. Your tool is wonderful!

In the last few days I have had a problem with the whatsapp connection.

After scanning the qr code and returning the connected status, it is not possible to send or receive messages.

Below is one of the logs I get after the connection.

After this response, it is impossible to send messages.

Best regards

Environment

I'm using a LINUX environment With the latest node version.

github-actions[bot] commented 1 year ago

Thank you for joining our community, happy. We are currently fixing this bug, our new version will be released soon.

Working with Love!

matheusverri commented 1 year ago

Morning, dude! Could you send your log, please?

dgabriel2334 commented 1 year ago

Good afternoon Matheus, I saw that you are Brazilian, but anyway I will send you the English version too!

The following happens. I can scan the connected qr code and it returns status, but after that I can't send messages or do any other action in the API.

Boa tarde Matheus, vi que você é brasileiro, mas de qualquer modo vou mandar a versão em inglês também!

Acontece o seguinte. Eu consigo escanear o qr code conectado e ele retorna status, mas depois disso eu não consigo mandar mensagens ou fazer qualquer outra ação na API

LOGS: info: https://orkestral.io - official site!

info: [example-asd1231das89h192n9da] Waiting... checking the browser... webhooks connect status.... info: [example-asd1231das89h192n9da] Browser successfully opened info: [example-asd1231das89h192n9da] checking headless... info: [example-asd1231das89h192n9da] headless option is active, browser hidden info: [example-asd1231das89h192n9da] Checking page... webhooks connect status.... webhooks connect status.... info: [example-asd1231das89h192n9da] Page successfully accessed webhooks connect status.... webhooks connect status.... webhooks connect status....1das89h192n9da]: Waiting page load

(QR CODE)

webhooks status message....1das89h192n9da]: Waiting for QRCode Scan... ✓ [instance: example-asd1231das89h192n9da]: Connected webhooks connect status....

itsfks commented 1 year ago

Estou com o mesmo problema, após conectado, mesmo setando um client.onmessage como sugerido na documentação, o mesmo aparentemente ignora e sequer visualiza a mensagem.

matheusverri commented 1 year ago

Também estou com o mesmo problema. Aparentemente está conectado, porém não consigo fazer nenhuma requisição pois a sessão não parece estar funcionando.

itsfks commented 1 year ago

Exato, o mesmo ocorre comigo. Todas as verificações acontecem, a sessão conecta, mas nada acontece. No meu código tentei os mesmos passos da documentação, e mesmo programado para receber uma mensagem, nada acontece.

bielgvs commented 1 year ago

Hello

I'm having a similar problem.

I can receive messages but when I try to send a answer I got some errors related to WAPI everytime I try to call some Venom related method

UnhandledPromiseRejectionWarning: Error: Evaluation failed: TypeError: Cannot read property 'isWidlike' of undefined at Object.window.WAPI.window.WAPI.sendCheckType (venom-bot\dist\lib\wapi\wapi.js:1:3)

The odd part of this is that sometimes it just works, like nothing was happening, and if I let the program running it goes with no problem.

Other times it gives this error and don't work.

itsfks commented 1 year ago

Estava considerar migrar do wa-automate para o venom, principalmente por economia no consumo de recursos. Mas infelizmente o venom aparenta ser mais problemático :/

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale.