Closed GoogleCodeExporter closed 9 years ago
It is a shame the logs *start* with that unexpected message, although it leads
me to conclude the comment in the code is wrong - that the xmpp lib may call
that function even when we didn't explicitly request a disconnect (ie, that if
something in the code triggered an explicit disconnect request, I'd expect to
see evidence of that in the logs too) It probably just means we need to make
that code identical to the "error disconnection" case and auto reconnect.
Original comment by skippy.hammond@gmail.com
on 7 Jan 2011 at 11:50
It's a normal disconnect that's not initiated by GTalkSMS (xmpp server side?).
Until now, this "error" was manage as a normal xmpp stop.
It's now managed as an error and reconnection process is started.
Original comment by Florent....@gmail.com
on 8 Jan 2011 at 12:56
Fixed in v1.7
Original comment by Florent....@gmail.com
on 8 Jan 2011 at 11:33
Original comment by fschm...@gmail.com
on 25 Aug 2011 at 7:51
Original issue reported on code.google.com by
fschm...@gmail.com
on 7 Jan 2011 at 4:18