-
Notifications
You must be signed in to change notification settings - Fork 496
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
cannot unmarshal array into go value of type map[string]interface {} #631
Comments
Yes..me. I tried this:
but it still doesn't work for me. If you look at the other open issues, this may not be fixable (unless someone can tell me how to fix??) It does however look like this library is not a long term solution --> #622 |
Changing for |
… On Wed, Nov 3, 2021 at 3:35 PM Maéverson Waitman ***@***.***> wrote:
Changing for SetClientVersion(2, 2142, 12) as last version of WhatsApp
Web .. still fails.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#631 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDLT23JZHXLTCC53ZU6WATUKE3BJANCNFSM5HI4TIXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
btw, about the issue: |
@beshoo I updated go-whatsapp to the same version of your project's go.mod ( |
I was able to get the raw message: Edit: |
Work's here with another random number. |
Thanks, I can confirm that |
Hi.
My API works fine until last monday (01 Nov 2021).
Today, I can't generate QRCODE. API return this message:
{"label":"http-access","level":"error","msg":"error decoding login resp: json: cannot unmarshal array into go value of type map[string]interface {}\n","service":"go-whatsapp-rest","time":"2021-11-03T10:00:46.488955064-03:00"}
Someone get this error too? It's the end?
Thanks.
The text was updated successfully, but these errors were encountered: