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 [ReferenceError]: WAPI is not defined #2680

Closed
matheusbsant opened this issue Apr 1, 2024 · 16 comments
Closed

Error [ReferenceError]: WAPI is not defined #2680

matheusbsant opened this issue Apr 1, 2024 · 16 comments
Labels
needs triage Needs avaliation question Further information is requested

Comments

@matheusbsant
Copy link

matheusbsant commented Apr 1, 2024

Does anyone have an estimate of when this problem will be resolved? Several people have already opened a call here, I tested all the "supposed" solutions and it didn't help. Could it be an update error? A "bug" in the library? I know that I need this to be resolved as soon as possible, the company I work for depends a lot on this functionality.

@matheusbsant matheusbsant added needs triage Needs avaliation question Further information is requested labels Apr 1, 2024
@codexJoin
Copy link

Does anyone have an estimate of when this problem will be resolved? Several people have already opened a call here, I tested all the "supposed" solutions and it didn't help. Could it be an update error? A "bug" in the library? I know that I need this to be resolved as soon as possible, the company I work for depends a lot on this functionality.

Delete the folder "tokens" and try again.

@alxcancado
Copy link

Does anyone have an estimate of when this problem will be resolved? Several people have already opened a call here, I tested all the "supposed" solutions and it didn't help. Could it be an update error? A "bug" in the library? I know that I need this to be resolved as soon as possible, the company I work for depends a lot on this functionality.

Delete the folder "tokens" and try again.

I just did that and does not work

@farleyBatista
Copy link

Same error here, but it doesn't go beyond the Checking is logged... option.

@codexJoin
Copy link

Same error here, but it doesn't go beyond the Checking is logged... option.

This is happening because the npm Node version is not up to date.
To fix this, use the following commands:

  1. npm remove venom-bot
  2. npm install --save orkestral/venom

That should make it work again.

@farleyBatista
Copy link

O mesmo erro aqui, mas não vai além da opção Verificando está registrado....

Isso está acontecendo porque a versão do npm Node não está atualizada. Para corrigir isso, use os seguintes comandos:

  1. npm remove veneno-bot
  2. npm install --save orkestral/venom

Isso deve fazer funcionar novamente.

When running the command npm install --save orkestral/venom, it displays the error below:

npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -4058
npm ERR! enoent An unknown git error occurred
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in: C:\Users\farle\AppData\Local\npm-cache_logs\2024-04-02T22_32_19_228Z-debug-0.log

@gschneider17
Copy link

Hola, actualizando Node descargandolo desde la pagina oficial volvió a funcionar en mi caso. Espero sirva...

@dgabriel2334
Copy link

I have a solution for this, it's like a brazilian dialect "gambiarra" but this works

You need install venom via npm with this command "npm install github:orkestral/venom" for the latest (master branch)

Then you need in node_modules path and navigate to venom-bot/controllers/browser.js then comment the line 44.

require("node-fetch");

This fix for me!

@BhagavatiAntala
Copy link

TypeError: Cannot set properties of undefined (setting 'session')
Getting this error on latest script

@pedro0506
Copy link

I have a solution for this, it's like a brazilian dialect "gambiarra" but this works

You need install venom via npm with this command "npm install github:orkestral/venom" for the latest (master branch)

Then you need in node_modules path and navigate to venom-bot/controllers/browser.js then comment the line 44.

require("node-fetch");

This fix for me!

Yeees, this work for me! =)

@dgabriel2334
Copy link

dgabriel2334 commented Apr 3, 2024

TypeError: Cannot set properties of undefined (setting 'session') Getting this error on latest script

Try this!
#2680 (comment)

@BhagavatiAntala
Copy link

TypeError: Cannot set properties of undefined (setting 'session') Getting this error on latest script

Try this! #2680 (comment)

same issue after commenting this require("node-fetch");

@dgabriel2334
Copy link

dgabriel2334 commented Apr 3, 2024

TypeError: Cannot set properties of undefined (setting 'session') Getting this error on latest script

Try this! #2680 (comment)

same issue after commenting this require("node-fetch");

Can you send the code where you start a new session ?

If you can send me the error log.

We can debug this and fix your issue

@thiagoalvesfoz
Copy link

I was having this same problem

A new release corrected all my problems like WAPI is not defined that I was facing in the last few days.

  • remove venom-bot
  • remove folder tokens/
npm install venom-bot@5.1.0

@orkestral
Copy link
Owner

We have support for Venom for just $15 per month, if you are interested, call our support via the link: https://web.whatsapp.com/send?phone=5561985290357

@matheusbsant
Copy link
Author

Installing this new version the problem was resolved here too.

@farleyBatista
Copy link

npm install venom-bot@5.1.0

This "gambiarra" worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Needs avaliation question Further information is requested
Projects
None yet
Development

No branches or pull requests

10 participants