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

Cant login #170

Closed
b4-io opened this issue Jun 11, 2019 · 19 comments
Closed

Cant login #170

b4-io opened this issue Jun 11, 2019 · 19 comments

Comments

@b4-io
Copy link

b4-io commented Jun 11, 2019

error during login: error decoding login resp: json: cannot unmarshal array into Go value of type map[string]interface {}

login successful, session: {uocSvrqQWvColFnkQ0aW2w== [] [] }

go func() {
		terminal := qrcodeTerminal.New()
		terminal.Get(<-qr).Print()     //err here
	}()



I have no session in /tmp, the problem generates when trying to generate QR code. Ive already updated to last version of the repo.
Thanks in advance

@iileandro
Copy link

Same problem here. Anybody knows the cause?

@hrizal
Copy link

hrizal commented Jun 12, 2019

error logging in: error during login: error decoding login resp: json: cannot unmarshal array into Go value of type map[string]interface {}

Yups

@zeftcool
Copy link

i found same problem.
fixed by change
longClientName and shortClientName with the short string

@reznikartem
Copy link

i found same problem.
fixed by change
longClientName and shortClientName with the short string

Hello. Can you provide working code example?

@reznikartem
Copy link

We receive error error on login:
decoding login connResp: json: cannot unmarshal array into Go value of type map[string]interface {}
Json is: ["Cmd",{"type":"update"}]

I suppose, that problem not in longClientName and shortClientName :(

@Rhymen, we are waiting for you! :)

@it-sumanp
Copy link

session.go file line number 152.
changing {0, 3, 225} to {0,3,3324} did solved it.

@it-sumanp
Copy link

I got this value from chrome but I did not understand the actual issue here, can anybody help ?

@tulir
Copy link
Collaborator

tulir commented Jun 12, 2019

The problem seems to be that whatsapp is disconnecting users with old whatsapp protocol versions. go-whatsapp probably just needs to update the protobuf schema and that number in session.go (and also keep updating those every time they change)

@reznikartem
Copy link

session.go file line number 152.
changing {0, 3, 225} to {0,3,3324} did solved it.

Thank you, it`s solved our problem!

@tulir
Copy link
Collaborator

tulir commented Jun 12, 2019

Note that the version number is in two places: https://github.com/Rhymen/go-whatsapp/blob/master/session.go#L152 and https://github.com/Rhymen/go-whatsapp/blob/master/session.go#L306

Restoring sessions might not work if you don't change the one on line 306 too.

@Romerito007
Copy link
Contributor

@tulir I checked on your fork that you updated protobuf. Right?

@tulir
Copy link
Collaborator

tulir commented Jun 12, 2019

Yes, although it looks like there's another protobuf update since then (version 3324, it was at 2846 when I updated).

@emauro
Copy link

emauro commented Jun 12, 2019

Using the last commit solves the problem.

@Romerito007
Copy link
Contributor

Thank you!

@franklinsales
Copy link

How @it-sumanp told:

session.go file line number 152.
changing {0, 3, 225} to {0,3,3324} did solved it.

And how @tulir told it's necessary update in the same file(session.go) at line 306 too.

Thx it's worked to me.

@leoteixeira2016
Copy link

work?

@b4-io
Copy link
Author

b4-io commented Jun 12, 2019

What made it for me was to change server, i just copied all my files into a backup server i have and started working. Dont know why though

@houstondapaz
Copy link
Contributor

I thinks this issue was resolved with the last commits @SchulteMK

@b4-io b4-io closed this as completed Jun 14, 2019
@b4-io
Copy link
Author

b4-io commented Jun 14, 2019

What was happening is I was updating the wrong folder, after i went to /go/src/github.com/Rhymen/go-whatsapp un updated de git it worked just fine in the other server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests