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.
The following was reported on the mailing list:
I have followed (to the letter) the instructions for installing MonoDroid on
the Mac and am coming up on issues when I try to build the MonoCross demo
for the Android emulator.
Mostly seems to be issues between MonoDroid and MonoDevelop, When I load the
MonoCross project in MonoDevelop I get the following error message:
System.NullReferenceException: Object reference not set to an instance of an
(MonoDevelop.Components.Commands.CommandInfo info) [0x00011] in
(MonoDevelop.Components.Commands.CommandInfo info) [0x00000] in
MonoDevelop.Components.Commands.CommandInfo info) [0x00079] in
(System.Object commandId, MonoDevelop.Components.Commands.CommandTargetRoute
targetRoute) [0x001a9] in
My first confusion is with all the references to "/User/michael", since this
directory is invalid and I have never entered "michael" into the system, so
I'm assuming there's some left over user specific script somewhere?
After the error message goes away I can build the project with no issues,
however when I hover over the "Run on" option to expand it and run on the
emulator I get a similar error and MonoDevelop will crash shortly after.
I am using the latest (2.6) beta for MonoDevelop and the versions of all the
software are within what the setup page demands. I'm doing preliminary work
for a company that is contemplating using this on a project very soon so
whether we use (and pay for) MonoDroid or another approach depends heavily
on whether we can get it running reliably.
I wish we could erase absolute path information from debug symbols, lots of users seem to be confused by seeing my name in stack traces.
The user is using an old MD, this was fixed in commit https://github.com/mono/monodevelop/commit/304f684d71000f4505dcc8638e1b79f7ee4f2852
This fix was included in MD 2.6b3, hoever in some cases the old addin from MD 2.6b2 may override it. That's fixed by the new addin from the addin manager.
Today, we have checked this issue with:
XS 4.2.4(build 266)
We are successfully able to load the solution in XS, without any crash. Hence closing this issue.