Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Step To Reproduce:
1.Launch the MonoDevelop.
2.Click on "Start a New Solution" link.
3.Choose C# > Mono for Android in left hand panel.
4.Select Mono for Android Application from the center panel.
5.Create a new solution.
6.Build thhe solution and then Run the solution.
7.Select the emulator.
8.Observe that the application does not run successfully.
The application does not run successfully, as when try to run the application, Unhanded exception occurs. i.e :
I/monodroid-gc( 358): environment supports jni NewWeakGlobalRef
E/MonoDroid( 358): Could not load type 'jatin.Activity1, jatin, Version=1.0.4345.28634, Culture=neutral, PublicKeyToken=null'. Skipping JNI registration of type 'jatin/Activity1'.
E/mono ( 358):
E/mono ( 358): Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
E/mono ( 358): at Android.Runtime.TypeManager.n_Activate (IntPtr jnienv, IntPtr jclass, IntPtr typename_ptr, IntPtr signature_ptr, IntPtr jobject, IntPtr parameters_ptr) [0x00000] in <filename unknown>:0
E/mono ( 358): at (wrapper native-to-managed) Android.Runtime.TypeManager:n_Activate (intptr,intptr,intptr,intptr,intptr,intptr)
Error should not appear and the application shoult run successfully.
MonoDevelop 3.0 Beta-1 (2.9.0)
Mono for Android 4.0
Mac 10.6 (Snow Leopard)
This issue exists only when the active configuration is Debug. However, it works fine when the active configuration is Release.
We believe that this is the FastDev bug.
Could you try again with the new packages that we are about to release in a few hours?
Also, for Mono for Android bugs, would you mind adding to the reporting:
* What API target level you are using (from the project options)
* the version of the Android simulator that you were using (this is the version of the simulator that you created).
You also should not be testing the MonoDevelop Beta against the Stable version of Mono for Android.
We have tested this issue with the new installers, i.e
Mono for Android 4.0.1
And now this issue does not exist.
Hence, closing this issue.