Hi Rolf - I'd say that you'd be correct except that it looks like we're both using a basic HttpWebRequest/HttpWebResponse pattern. Not even using the streams directly, certainly no sockets directly. One of my users on an iPodTouch seems to be able to reproduce this more often. Not sure if that is because it's a single CPU device or not.
Anyway, it is a big problem because it leaves the app in a completely unusable state. In the linked StackOverflow example (earlier in this thread), I was using a web reference to a WCF service similar to what bamagrad showed. I'm currently still seeing this after changing the network stack completely to using ServiceStack on both client & server. Best, Paul -- View this message in context: http://monotouch.2284126.n4.nabble.com/ConnectFailure-error-causes-app-to-cease-connecting-externally-tp3931899p4656317.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
