http://bugzilla.novell.com/show_bug.cgi?id=555439
http://bugzilla.novell.com/show_bug.cgi?id=555439#c8 Miguel de Icaza <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Miguel de Icaza <[email protected]> 2009-12-04 04:33:49 UTC --- I tested this with a 3G on ATT in the following conditions: * Disabled WiFi * Enabled 3G => Application works * Disabled WiFi * Set airplane mode, reset it back to normal * Launch application while still "searching...." => Application produces Socket error. As soon as the 3G indicator comes up, I no longer get an error. * Disable WiFi * Disable 3G => Application gets sockets errors, invalid hostnames (and so does Safari) Eventually, the phone gets network connectivity (Edge in my case), so we end up with: * Disabled WiFi * Disabled 3G * Edge running => Connection works. It does take a while, some 10 seconds to go from 3G to Edge working though. I have noticed problems like the symptoms described in the bug with my twitter client depending on where I am though; Sometimes I am in a bad spot, and even with 3G I get errors from it. See the sample monotouch-samples/reachability for some samples on how to detect the network availability. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
