-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
i can't run the script #3073
Comments
I have the same problem |
I had several issue when trying to start the session. For both cases ^1.23.0 version used, node 18, linux, browser chromium. Idk if it's related to this topic, but got this issue today.
|
yes i have same problem |
If you are running linux, try to create a new user and run the code as the new user. |
I have the same problem running on Windows or Ubuntu Server. |
3 Jun 15:07:00 - [info] [whatsappLink:Web] Status : Connecting to Whatsapp... |
Try adding this to you config object when initializing new Client:
|
it give me now: ReferenceError: clientObj is not defined` |
i have same problem. could you please help me ? |
what is the mean 1.23.-1 alpha? |
Fixed #3073 You have to pass local Auth
|
change the whatsapp-web.js to "^1.23.1-alpha.6" on your package.json |
oo i see.ok fix it with ur comment. thx all |
what the filename and path should i edit? |
no need to pass filename or path just install the both packages and copy this code and run it it will show QR code in the console scan it and that's it |
root@ed9133fc9883:~/.node-red/node_modules# node-red Welcome to Node-RED4 Jun 04:02:51 - [info] Node-RED version: v3.1.9 Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials You should set your own key using the 'credentialSecret' option in
|
it worked thanks |
I have the same problem and the solutions provided here have not worked for me, does anyone have any other suggestions? the error is: C:\Users\Gateway\Documents\APM MENSAJE\programas\prospectador> node prospectador.js
TypeError: Cannot read properties of null (reading '1')
|
it worked, thanks |
Hello your happen have a resolve for this |
Hi,
|
can you check your email i sent you an email to talk |
I didint received it you can also check i have working example here it is linked with openai assistant https://github.com/RaheesAhmed/openai-assistant-with-whatsapp-web |
Hello, Do I Need another version? |
Hi guys, do you know why whatsapp-web is so unstable, all the time just stopping to work? |
In which file do I make this change? |
Hi everyone, I'm having an issue with the 'authenticated' event, I can scan QR but then nothing happens, not any logs or errors form any package, below is the object I am using in my script new Client({ Wonder if a version is working fine |
Credits for @BenyFilho from Discord. Using version Exodus WhatsApp Web 2.30xx: Using version WhatsApp Web 2.24xx:
3- delete folder node_modules and wwebjs_auth; |
How do I remove WebCache or in which file should I pass the type: "remote" information? |
You don't need pass it, just initialize the client normally. Example:
|
Is there an existing issue for this?
Describe the bug
i get that error
reject(new Error([
^
Error: Failed to launch the browser process!
[0603/104054.851572:ERROR:zygote_host_impl_linux.cc(99)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Expected behavior
i expect the code to work but it never
Steps to Reproduce the Bug or Issue
use the code
Relevant Code
const qrcode = require('qrcode-terminal');
const { Client } = require('whatsapp-web.js');
const client = new Client();
client.initialize();
client.on('qr', (qr) => {
qrcode.generate(qr, { small: true });
});
client.on('ready', () => {
console.log('Client is ready!');
});
client.on('message', (message) => {
if (message.body === 'hello') {
message.reply('Hiiiii');
}
});
Browser Type
Chromium
WhatsApp Account Type
Standard
Does your WhatsApp account have multidevice enabled?
Yes, I am using Multi Device
Environment
linux/arch64
Additional context
No response
The text was updated successfully, but these errors were encountered: