Client fires "error" event for 60 second timeout, timeout handlers >60s never fire

[thully]

In debugging server timeout issues, I found that the socket.io-client-swift always fires an error with the text "The request timed out." after 60 seconds of a connection attempt. This happens regardless of whether a timeout handler is set - if there is one and it is set for less than 60 seconds, it gets fired in addition to the error unless the socket is disconnected by the handler. If there is a timeout handler set for greater than 60 seconds, it never gets fired.

It seems like timeouts should be handled by the timeout handler exclusively, and should not trigger an error. 60 seconds may make sense as a default, but greater values specified by the user should be accepted unless the API explicitly specifies a maximum timeout value.

[nuclearace]

That error is mostly likely coming from the URLSession itself timing out. https://github.com/socketio/socket.io-client-swift/blob/master/Source/SocketEngine.swift#L271

Which gets communicated up when it times out. I'm not sure how to best solve this issue.