search

Rhymen / go-whatsapp

WhatsApp Web API
MIT License
2.05k stars 490 forks source link

Error getting QrCode #604

Closed LucasSPanaro closed 2 years ago

LucasSPanaro commented 2 years ago

I got an error while Connecting: "message":"wppservice.loop: Connection failed: interface conversion: interface {} is nil, not string"

My version is: {2, 2121, 6}

Does anyone have a similar problem?

bhavesh53 commented 2 years ago

@LucasSPanaro update to latest version {2, 2126, 14} in session.go file

LucasSPanaro commented 2 years ago

It worked, Thanks!

LucasSPanaro commented 2 years ago

Got the same error again, with whatsappBusiness, version 2.21.14.24: "wppservice.loop: Connection failed: interface conversion: interface {} is nil, not string"

paulocsanz commented 2 years ago

Got the same error again, with whatsappBusiness, version 2.21.14.24: "wppservice.loop: Connection failed: interface conversion: interface {} is nil, not string"

Whatsappweb works and sends 2.2126.14, but it doesn't work with go-whatsapp sending the same payload. It answers with: [\"Cmd\",{\"type\":\"update\"}]

paulocsanz commented 2 years ago

It seems the connection fail error changed to timeout.

Now most of our clients are connected with 2.2126.14, but they are getting timeout when trying to send new messages.

Anybody experiencing something similar?

borigoto commented 2 years ago

We have same problema..

"Websocket keepalive for 0xc0002e8b40 failed: connection timed out"

Stay on air few minutes and down...

Em 02/08/2021 14:18, Paulo Cabral Sanz escreveu:

It seems the connection fail error changed to timeout.

Now most of our clients are connected with 2.2126.14, but they are getting timeout when trying to send new messages.

Anybody experiencing something similar?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Rhymen/go-whatsapp/issues/604#issuecomment-891195996, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWBCCSGDED6YFV77DNSDJLT23HO7ANCNFSM5BMY3ESA.

paulocsanz commented 2 years ago

It seems we fixed it by increasing the NewConn timeout, anybody experiencing the same?

Nelsonguiana commented 2 years ago

Parece que corrigimos aumentando o tempo limite do NewConn, alguém experimentando o mesmo?

Changed the time for how many Paulo?

paulocsanz commented 2 years ago

20s seems to fix most, we still have a few clients complaining, but from 1000 numbers broken it went to 4. But those not even 2 minutes fixed it, so the problem may be elsewhere.