Skip to content
This repository has been archived by the owner on May 9, 2019. It is now read-only.

Losing ACKs when sending messages #74

Open
BrendoBomfim opened this issue May 9, 2018 · 2 comments
Open

Losing ACKs when sending messages #74

BrendoBomfim opened this issue May 9, 2018 · 2 comments

Comments

@BrendoBomfim
Copy link

Hi guys, after the last update I've noticed that the ids have changed to HEX like this:

DEBUG:zap.layer:text
DEBUG:zap.layer:Received Message:
ID: D66065392ED4B9ECE25A5485D84B80F3
From: [email protected]
Type:  text
Timestamp: 1525871430
Body: b'Hello'

But when I do send the ids are numbers:

DEBUG:zap.layer:Sending Message:
ID: 1525871303-3
To: [email protected]
Type:  text
Timestamp: 1525871443
Body: b'World'

And after some time, usually after 5 minutes I get this:

DEBUG:yowsup.layers.logger.layer:rx:
<stream:error>
<ack id="1525871303-3">
</ack>
</stream:error>

ERROR:yowsup.layers.interface.interface:Stream Error type: ack
{'ack': None}

INFO:yowsup.layers.interface.interface:Initiating reconnect
DEBUG:yowsup.layers.protocol_iq.layer:stopping ping thread
DEBUG:yowsup.layers.network.layer:Disconnected, reason: Requested
DEBUG:yowsup.layers.protocol_iq.layer:YowPingThread-2 - ping thread stopped

@Aragur
Copy link
Owner

Aragur commented Jun 6, 2018

Are you sending the acks manualy?
Are you using the CLI?

@pabloruan0710
Copy link

pabloruan0710 commented Jun 7, 2018

I have the same problem, after logging in by the CLI I can not receive the messages, but I can send, I get the following ack

<ack type="retry" class="receipt" from="55619****[email protected]" id="71022C42562799D1C8789BB964B65992">
</ack>

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

No branches or pull requests

3 participants