I just solved this a moment ago. It seems if im using .NET sockets and GKSession at the same time, the sockets act in an unpredictable manner. As soon as I disabled the GKSession, the socket code worked perfectly.
I will try put together a sample app that shows this behaviour and submit as a bug, hopefully its a bug in Mono/MonoTouch that can be fixed, as I need both these features working at the same time in my app. (I use GKSession for bluetooth clients, but Sockets are far faster than GKSession on Bluetooth/Wifi for users who are on same WiFi network as host, plus I need sockets to communicate with a server). -- View this message in context: http://monotouch.2284126.n4.nabble.com/Serious-strange-problems-with-Sockets-TcpClient-tp4595780p4610777.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
