Not authorized
Since a couple of hours all my running numbers get not-authorized... using this master branch. I didnt do nothing on my side like sending messages etc. Someone experiencing this also? Any ideas? Did they change the token again?
Reported also in #74 and https://github.com/mgp25/Chat-API/issues/1840
@jlguardi it happens on old numbers also... maybe they changed something
same here, but I had a number I was not using.... I tried to use it and it works! so apparently they might have ran some sort of scan and blocked all the connected accounts
i think invalid signature messages are causing blocks. what do you think?
I got banned several times without sending even 1 message:
- Register a REAL number with the real application
- Use it, send a message normally. all is well.
- Register again using Yowsup.
- Login using Yowsup.
- Presence: available.
- Presence: subscribe to some numbers.
- Wait for incoming messages, mark them as Read when they arrive. [We receive commands and control a Linux server from a far using that]
- No outgoing messages at all.
This happened with several different numbers.
What do you mean by signature messages?
As said in the other thread, media messages or group messages might end in an "Invalid signature!" error. This results in an unACKed message.
I'll check for invalid signature exception (probably due to mixing executions of yowsup from different servers) and I'll try to manage correctly. However, today I got banned an account without messages (in/out) for a year but online all the time (but computer reboots). So I guess that the cause isn't media messages.
i retried the stuff with the invalid signatures. whatsapp kicks you out after approx 10ping, if you dont ack the message (but you are still online):
<ack type="retry" participant="[email protected]" from="[email protected]" class="receipt" id="046767B4151CD907DD9BCAAF1FB752">
</ack>
DEBUG:yowsup.layers.logger.layer:rx:
<message participant="[email protected]" notify="KFreeman" from="[email protected]" type="media" id="046767B4151CD907DD9BCAAF1FB752"
t="1461787861">
<enc count="1" type="msg" mediatype="audio" v="2">
approx 10 pings later (note the id is the same as the one, that was not acked!):
DEBUG:yowsup.layers.logger.layer:rx:
<stream:error>
<ack id="046767B4151CD907DD9BCAAF1FB752">
</ack>
</stream:error>
Definitely not the signatures. Or at least not JUST the signatures. Like @jlguardi , I also got this error with no messaging at all.
I'll try to fix "invalid signature" as "invalid MAC" but this isn't the cause to being banned (I guess).
Some here. My number get banned.
Connected a new number, didn't send any messages. After two days running it got blocked.... How do they detect and block us??? someone have a clue???