I am using a custom C# DDP library to connect to my server, using an unstable mobile connection. Since it’s a mobile device, it might go to sleep anytime.
So I check on wakeup if the WebSocket connection has been broken. If so, I re-connect and resume the session with an
login message (method call) with a resume token.
This works most of the times. The server first responses with an UPDATE on the method, and then with a RESULT containing a the same token, a user id and an expiry date.
However, somestimes, the UPDATE is sent, but not the RESULT. This causes my app to “hang”, because the login handshake hasn’t completed.
I am wondering why this happens. Could it be that the server won’t send a result on a login request if it thinks that it’s still connected (although the client thinks otherwise)?