Just getting started here so sorry if this is a no brainer but I guess my expectation of at least the sample code working out of the box was too great. I downloaded the tasky sample and opened it within VS2012. When I hit run, it fails with only this in the output window. Nothing appears out of the ordinary except for the last line where mono is exiting with code 0. It shouldn't be exiting, not until I close the application, methinks.
I am running on x64 Windows 8, VS2012.
04-30 12:51:54.095 I/ActivityThread( 2726): Pub com.xamarin.samples.taskyandroid.mono.MonoRuntimeProvider.__mono_init__: mono.MonoRuntimeProvider 04-30 12:51:54.115 D/dalvikvm( 2726): Trying to load lib /data/data/com.xamarin.samples.taskyandroid/lib/libmonodroid.so 0x40513310 04-30 12:51:54.115 D/dalvikvm( 2726): Added shared lib /data/data/com.xamarin.samples.taskyandroid/lib/libmonodroid.so 0x40513310 04-30 12:51:54.206 W/MonoDroid-Debugger( 2726): Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8957,server=y,embedding=1 04-30 12:51:54.566 W/MonoDroid-Debugger( 2726): Accepted stdout connection: 34 04-30 12:51:56.446 W/monodroid-gc( 2726): GREF GC Threshold: 1800 Loaded assembly: /data/data/com.xamarin.samples.taskyandroid/files/.__override__/TaskyAndroid.dll Loaded assembly: /data/data/com.xamarin.samples.taskyandroid/files/.__override__/Tasky.Core.Anroid.dll Loaded assembly: Mono.Android.dll [External] Loaded assembly: System.Core.dll [External] 04-30 12:51:57.706 W/MonoDroid( 2726): Xamarin/Android Trial Mode Active In mgmain JNI_OnLoad The program 'Mono' has exited with code 0 (0x0).
Posts
This is possibly bug 11803.
What Android version is your emulator running? You can try waiting a few seconds and then attempt to Debug again, though on Android 4.2 you may need to wait ~20s before trying to Debug again.
I am using the MonoForAndroid_API_10. So what is that Android 2.2 or something?
Yes that bug looks like what I am running into. I am using Xamarin.Android v4.6.04000 just as the person who found the bug was using. I just downloaded Xamarin yesterday. When will this fix make it to general availability? Is there a workaround for me until then?
API level 10 is Android v2.3.3.
So am I not able to target Andriod 2.3 until that bug is fixed?
You can try the workaround I mentioned: try waiting a few seconds and then attempt to Debug again.
I got the same issue... Just keep the emulator running and give some time to device for worm up. After that just start debugging the application it will run.
Please let me know if any further information needed.