-
-
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
[BUG] qrcode not printing because 405 error #912
Comments
Sorry, try doing it like this.import makeWASocket, { const sock = makeWASocket({ sock.ev.on("creds.update", saveCreds);
}); |
Sorry, try doing it like this.import makeWASocket, { const sock = makeWASocket({ sock.ev.on("creds.update", saveCreds);
}); |
Still same.... |
Retry to running in linux
Pada Sen, 15 Jul 2024 19.14, darkshadowside1 ***@***.***>
menulis:
… Still same....
—
Reply to this email directly, view it on GitHub
<#912 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3BQIJRLQVLGVQKXEE65V6DZMOVKHAVCNFSM6AAAAABKPI3MJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYGI2TIOBTHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think this may be a problem from the build from TS to JS, when I run the same code with in this project (Baileys-master) it runs as expected but when i run the same with the baileys as a dependency it does not work. |
I THINK THAT'S BECAUSE YOUR IP BLOCKED BY WHATSAPP USE A PROXY TRY. STILL THE SAME ERROR TRY ADDING A VERSION TO
|
I am just running the sample code given in the main page
Steps to reproduce the behavior:
Expected behavior
QR or pairing code should be printed out
Environment (please complete the following information):
I am running it on windows 11
Additional context
I have tried using different methods, I have tried changing version: [2, 2413, 51], and i have tried using [email protected] but still the issues is same.
I have also noticed that location in data changes everytime i runt the application, i don't know if it is supposed to run that way
The text was updated successfully, but these errors were encountered: