Eric & Jon,
My apologies, the Mobile API's are not responsible.
I've got some updated stack trace information which seems to indicate a call
to "System.MonoType.GetProperties()" is the culprit.
http://mono-for-android.1047100.n5.nabble.com/Mono-crashing-at-System-MonoType-GetProperties-call-tp51
Hi Eric,
I can't see a file version on the Xamarin.Mobile.dll but it looks like it
was compiled on 8 Dec at 6:04pm?
I just downloaded the latest from the zip file and it looks like it is the
latest.
Regards
Derek
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/mg
Hi Derek,
There have been three releases of the Xamarin Mobile API Preview so far, do
you know which you are using?
If not, you can try the latest version from
http://xamarin.com/xamarinmobileapipreview.zip
On Mon, Jan 16, 2012 at 4:20 PM, devbuzz wrote:
> Hi Jon,
>
> I'm using the latest Mono
Hi Jon,
I'm using the latest Mono for Android AFAIK. - i.e. the fast version with
the great debugging :)
Using a process of elimination I have tracked the error down to the managed
Xamarin Mobile API.
Specifically it seems to occur in the geolocator.PositionChanged event
handler.
protected void
On Jan 16, 2012, at 5:34 AM, devbuzz wrote:
> I have an activity and a service which crash and completely lock up the
> device.
That's...very odd. :-/
Which version of Mono for Android is this? Which Android platform?
> I see the following in the log:
>
> *In mgmain JNI_OnLoad
> The program 'M
I have an activity and a service which crash and completely lock up the
device.
The service uses a number of thread timers to do some background processing
as some logging to SQLite.
I see the following in the log:
*In mgmain JNI_OnLoad
The program 'Mono' has exited with code 255 (0xff).
*
Does
