When using Ruffles as transport for MLAPI v11, when iOS client device has screen locked for over ~5 seconds, after the device is unlocked Ruffles library begins spamming error messages and the transport stops working entirely.
Error includes this exception in printout:
System.Net.Sockets.SocketException (0x80004005): The socket is not connected
Error message is being printed in the Socket's StartSocketLogic loop.
|
if (Logging.CurrentLogLevel <= LogLevel.Error) Logging.LogError("Error when receiving from socket: " + e); |
This issue appears to be identical to issue that is reported to LiteNetLib repo here:
RevenantX/LiteNetLib#312
For reference on solution, LiteNetLib fixed this issue in the following commits:
RevenantX/LiteNetLib@6142768
RevenantX/LiteNetLib@dac4fea
When using Ruffles as transport for MLAPI v11, when iOS client device has screen locked for over ~5 seconds, after the device is unlocked Ruffles library begins spamming error messages and the transport stops working entirely.
Error includes this exception in printout:
System.Net.Sockets.SocketException (0x80004005): The socket is not connected
Error message is being printed in the Socket's StartSocketLogic loop.
Ruffles/Ruffles/Core/RuffleSocket.cs
Line 947 in 6d940c6
This issue appears to be identical to issue that is reported to LiteNetLib repo here:
RevenantX/LiteNetLib#312
For reference on solution, LiteNetLib fixed this issue in the following commits:
RevenantX/LiteNetLib@6142768
RevenantX/LiteNetLib@dac4fea