You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a WebApi app in a VPS with Jabber-Net that connects to Google CCS, who notifies when a XMPP message arrives from an Android app on a device. Everything works perfect, but randomly, after 7, 10 hours, stops receiving messsage from CCS. No event is called (I captured every of them)
The text was updated successfully, but these errors were encountered:
Probably that's a network connection issue? Theoretically, Jabber-Net should generate error event in that case, but not every network issue can be reliably detected by client.
I'll check if Jabber-Net always calls error handlers on network errors.
I think that the general solution is to use XEP-0199: XMPP Ping to detect any network issues, but I don't think that ping is implemented in Jabber-Net. I'll create a feature issue for that (XEP-0199: XMPP Ping #80).
@toledomatias currently I'd recommend you to implement ping yourself. Joe Hildebrand, original Jabber-Net author, have written this excellent answer at StackOverflow that could help you.
I have a WebApi app in a VPS with Jabber-Net that connects to Google CCS, who notifies when a XMPP message arrives from an Android app on a device. Everything works perfect, but randomly, after 7, 10 hours, stops receiving messsage from CCS. No event is called (I captured every of them)
The text was updated successfully, but these errors were encountered: