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
{{ message }}
This repository has been archived by the owner on Aug 15, 2022. It is now read-only.
Version 26 from the asset store (Mar 20, 2019), Windows 10 1903
Expected behavior:
Attempt to connect to server 10 times with 3 second delays between attempts. If server is unreachable trigger connectAttemptFailed event on UDPClient.
Actual behavior:
//Snippet from UDPClient.ConnectTask.Queue(()=>{do{// Send the accept headers to the server to validateClient.Send(connectHeader,connectHeader.Length,Server.IPEndPointHandle);Thread.Sleep(3000);}while(!headerExchanged&&IsBound&&++connectCounter<CONNECT_TRIES);if(connectCounter>=CONNECT_TRIES){if(connectAttemptFailed!=null)connectAttemptFailed(this);}});
Attempts to connect once, a SocketException occurs in UDPClient.ReadNetwork, which triggers Disconnect(true) which ultimately results in IsBound on the client to be set to false, which pre-empts any further connection attempts.
Additionally because the connectCounter never increments, the connectAttemptFailed is never triggered.
Version Number and Operating System(s):
Version 26 from the asset store (Mar 20, 2019), Windows 10 1903
Expected behavior:
Attempt to connect to server 10 times with 3 second delays between attempts. If server is unreachable trigger
connectAttemptFailed
event on UDPClient.Actual behavior:
Attempts to connect once, a SocketException occurs in
UDPClient.ReadNetwork
, which triggersDisconnect(true)
which ultimately results inIsBound
on the client to be set to false, which pre-empts any further connection attempts.Additionally because the
connectCounter
never increments, theconnectAttemptFailed
is never triggered.Steps to reproduce:
Make sure to create your own
clientConnectFailed
,clientConnected
and/orclientBindFailure
functions to use this test code.#180 seems to indicate this is in some way related to IP parsing? But I'm not seeing how. In my case I'm trying to connect to
127.0.0.1
.The text was updated successfully, but these errors were encountered: