-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
Delete the folder "tokens" and try again. |
I just did that and does not work |
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.
That should make it work again. |
When running the command npm install --save orkestral/venom, it displays the error below: npm ERR! code 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 |
Hola, actualizando Node descargandolo desde la pagina oficial volvió a funcionar en mi caso. Espero sirva... |
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.
This fix for me! |
TypeError: Cannot set properties of undefined (setting 'session') |
Yeees, this work for me! =) |
Try this! |
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 |
I was having this same problem A new release corrected all my problems like
npm install venom-bot@5.1.0 |
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 |
Installing this new version the problem was resolved here too. |
This "gambiarra" worked for me. |
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.
The text was updated successfully, but these errors were encountered: