-
Notifications
You must be signed in to change notification settings - Fork 5
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
libwa not logging into wa #4
Comments
Hi,
I’m not actively using it, but I try to keep it working from time to time.
The error suggest that the server is rejecting the client version from connecting as it is too old. The libwa client version is currently set to 0.3.9309:
fd80e37
The WA server reports the current version every time you connect, and you may be able to find it using the inspect tool in the browser. The last version set by the go-whatsapp library is 2.2121.6, which should work just fine:
https://github.com/Rhymen/go-whatsapp/blob/447ed9cc617912e5242b65fc33cb42248bb1ee3c/session.go#L21
You may want to update the libwa client version and see if anything else breaks. I saw some other changes in the protocol, but it may be able to work fine if those are just additional features.
Rodrigo
… El 18 ago 2021, a las 0:08, JAHS ***@***.***> escribió:
Hi again rodrigo, i wasnt using this lib in some time and i cant see new commits to this project, are you still maintaining it? if yes, i was setting up the bitlbee-wa and i am getting this error regarding to not finding a "ref" key ni the response element at login.
dont know if in this 2 years the login response have chaged.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi again rodrigo, i wasnt using this lib in some time and i cant see new commits to this project, are you still maintaining it? if yes, i was setting up the bitlbee-wa and i am getting this error regarding to not finding a "ref" key ni the response element at login.
dont know if in this 2 years the login response have changed.
The text was updated successfully, but these errors were encountered: