On Oct 14, 2011, at 3:48 AM, SRI wrote:
> Warning. I am writing this from Memory when I last observed
> this error (few months back). This error is benign.
Different error. :-)
You're talking about this message:
> DEBUG/SntpClient(60): request time failed: java.net.SocketException: Address
011 04:13
To: Discussions related to Mono for Android
Subject: Re: [mono-android] System.Net.Sockets exception
Warning: I'm not known for being the smartest guy in the room. That said...
On Oct 13, 2011, at 8:47 AM, Nicklas Møller Jepsen wrote:
> The main problem is that I'm seeing com
h .NET version are Mono for Android
"using" or compatible with?
Thanks, Nicklas
-Original Message-
From: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Jonathan Pryor
Sent: 14. oktober 2011 04:13
To: Discussions related t
Hi Jon,
Warning. I am writing this from Memory when I last observed
this error (few months back). This error is benign.
This error last time I debugged deep into mono and found that this was
related to IPv4 and IPv6 Address Family checking, When I was porting
System.Web to Android/IOS and
Warning: I'm not known for being the smartest guy in the room. That said...
On Oct 13, 2011, at 8:47 AM, Nicklas Møller Jepsen wrote:
> The main problem is that I’m seeing completely different behavior when
> running the app from VS (on a device) compared to manually copying the APK to
> the sam
I never did get an answer for this one.
I will correct the problem as it is also causing the exception when I manually
copy the APK to a device and installs it.
I've tried both to use Debug and Release mode.
The main problem is that I'm seeing completely different behavior when running
the app
