Ok, so if i understand this correctly, one of the clients is somehow connecting with a broken connectioninfo, creating errors when the server tries to deserialize it.
… Yes. Although having said that it is unlikely to be in our library source otherwise we would have come across this already. It is entirely possible that this is caused by something else, but unless it’s possible to create a specific use case that demonstrates the failure reliably it is nearly impossible to fix. Some further questions:
1. Are you sending/receiving any ConnectionInfo objects yourself?
2. Try enabling packet check sum validation by placing the following at the start of your applications
NetworkComms.EnablePacketCheckSumValidation = true;
3. Consider logging to a txt file which will help track what occurred immediately before the error. Please see https://networkcomms.net/enable-logging/.
Regards,
Marc