Bug 201 - Crash while loading a solution.
Summary: Crash while loading a solution.
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 1.0
Hardware: Macintosh Mac OS
: --- major
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2011-08-05 13:38 UTC by Miguel de Icaza [MSFT]
Modified: 2014-03-27 07:20 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
VERIFIED FIXED

Description Miguel de Icaza [MSFT] 2011-08-05 13:38:05 UTC
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
object
 at MonoDevelop.MonoDroid.PublishApplicationHandler.Update
(MonoDevelop.Components.Commands.CommandInfo info) [0x00011] in
/Users/michael/Mono/md-2-6/extras/MonoDevelop.MonoDroid/MonoDevelop.MonoDroid/MonoDroidCommands.cs:223
 at MonoDevelop.Components.Commands.CommandHandler.InternalUpdate
(MonoDevelop.Components.Commands.CommandInfo info) [0x00000] in
/Users/michael/Mono/md-2-6/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandHandler.cs:47
 at MonoDevelop.Components.Commands.CommandManager.DefaultUpdateCommandInfo
(MonoDevelop.Components.Commands.ActionCommand cmd,
MonoDevelop.Components.Commands.CommandInfo info) [0x00079] in
/Users/michael/Mono/md-2-6/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:781
 at MonoDevelop.Components.Commands.CommandManager.GetCommandInfo
(System.Object commandId, MonoDevelop.Components.Commands.CommandTargetRoute
targetRoute) [0x001a9] in
/Users/michael/Mono/md-2-6/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:747


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.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-05 18:29:51 UTC
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.
Comment 2 Danish Akhtar 2014-03-27 07:20:07 UTC
Today, we have checked this issue with:

XS 4.2.4(build 266)
X.Android 4.13.0

We are successfully able to load the solution in XS, without any crash. Hence closing this issue.