Please sign in to comment.
Clean up ServiceConnection timer when we receive a result.
Previously, we could make a connection, do some method calls, and then 10 seconds later the connection happens to be dropped and the connection timer fires, which not only throws an unexpected error into the future, but also resolves the future twice. I think ServiceConnection is just supposed to time out if you don't hear anything from the server within 10 seconds, so it now no longer times out if you hear things from the server but then happen to be not connected when 10 seconds has elapsed.
- Loading branch information...