-
Notifications
You must be signed in to change notification settings - Fork 494
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
could not decode binary: invalid string with tag 174 #187
Comments
ok, it seems that whatsapp is going to add a new tag 174, or it is already added, in the whatsapp |
so @shekohex would you close this issue |
Actually, we need to know what tag it is, since definitely WhatsApp will update to this version soon, so we would face that issue. I managed to solve this by returning an empty |
hello, same error here "gowhatsapp: error occoured: error processing data: error decoding binary: could not decode binary: invalid string with tag 174" I hope you can fix it, thank you so much for your work! |
have no idea, i use Latest WhatsApp Version (Android 9) and latest go-whatsapp version, works like a charm |
The problem is linked with the version of phone whatsapp version, on my project I have a lot of numbers connecteds (more than 300) and sometimes this error is logged, but I don't have the phone to get more details |
are you in beta channel ? what whatsapp version you are using ? |
are you sure that it's a |
@shekohex my WhatsApp version is 2.19.188, and it's latest version available in play store, and i'm not beta-tester |
yup, but i'm using beta v2.19.190 and it has this problem. |
Has anyone tried to find a clue in the official WAweb js source? |
I found this code |
I'm afraid of the fact that could be a Decoder error, and there's no tag 174 at all. I will try to Inspect these bytes to see what's actually going on. |
Any update @shekohex ? |
not actually, i just bypass it as a workaround here by returning an empty node once i get that error, by the way, i hadn't encounter any new errors since i fixed this using this workaround, i mean by errors here: logic errors, server error, invalid data, data corruption ..etc. |
Hello, I changed the phone for one with Android 9 (I am using WhatsApp
business) and it works fine, randomly the '174 tag' ocurrs, but is not all
the time.
El lun., 15 jul. 2019 a las 20:56, Shady Khalifa (<notifications@github.com>)
escribió:
… Any update @shekohex <https://github.com/shekohex> ?
not actually, i just bypass it as a workaround here by returning an empty
node once i get that error,
i'm currently not using this project, as i said it helped me to implement
my own.
by the way, i hadn't encounter any new errors since i fixed this using
this workaround, i mean by errors here: logic errors, server error, invalid
data, data corruption ..etc.
all working now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#187?email_source=notifications&email_token=AK2LPBBD7M3UNRQD32YUVZDP7UFEJA5CNFSM4H6XPTT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ7JHLA#issuecomment-511611820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK2LPBHTLMMKPFWUVNJ6SXDP7UFEJANCNFSM4H6XPTTQ>
.
|
This (for me) was fixed with commit hoehermann/purple-gowhatsapp@47b0740 |
@Lantizia I'm don't found this commit |
Sorry I now realise why my commit mention before... wasn't turning into a link automatically :) I've been talking about purple-gowhatsapp rather than go-whatsapp... have updated the link above to reflect that. But if you are using purple-gowhatsapp then there is already a prebuilt binary of 47b0740 at https://buildbot.hehoe.de/purple-gowhatsapp/builds/ Sorry for the confusion |
@Lantizia understood But this commit did not fix the problem only mask the error, right? |
Couldn't comment, not my code. |
@houstondapaz I think I'm doing the same thing in my codebase, I didn't have any side effects thought. Moreover, that error happens only on starting, and occurs 3 or more times. I just ignore it 😌 |
I agree to ignore this error on your application, but we cannot ignore this error as a library |
On Android 9 with WhatsApp version 2.19.254 I had the same issue, updating WhatsApp version to 2.19.258 solved this - I no longer get the 174 tag on the server. Could potentially be a bug introduced and then removed by the WhatsApp team. |
Does anybody have an update on this? |
solution? |
May be related: rodarima/libwa#1 |
Hi, I also got this error. |
Still got this problem running the echo example
|
I have encountered the same problem in the whatsapp signal bridge here: meinto/whatsapp-signal-bridge#1 |
Hello, I got this error
Directly after scanning the QR
Here is some information
A small note here for the owner, i'm also working on another project uses the same implementation as this project, but written in rust, and of course since most of my code is ported from this project i'm now facing the same problem.
Here is a debug log from my implementation that maybe help
OPEN THE LOG
i'm open to provide more information as needed to reproduce this issue
Thanks :)
The text was updated successfully, but these errors were encountered: