Bug 8685 - Unexpected Error: file a report with xamarin
Summary: Unexpected Error: file a report with xamarin
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.1.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-11-30 00:03 UTC by GK
Modified: 2013-12-05 18:35 UTC (History)
3 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:
RESOLVED NORESPONSE

Description GK 2012-11-30 00:03:15 UTC
I get an unexpected error MT000 file a bug report with Bugzilla error

Then it shows me this error log:

Error while updating status of command: Monodevelop.iphone.iphonecommands.selectsimulatortarget

System.NullReferenceException: Object reference not set to an instance of an object
  at MonoDevelop.IPhone.AppleIPhoneSdk+<GetSimulatorTargets>c__IteratorA.MoveNext () [0x00000] in <filename unknown>:0 
  at System.Linq.Enumerable+<CreateWhereIterator>c__Iterator35`1[MonoDevelop.IPhone.IPhoneSimulatorTarget].MoveNext () [0x00000] in <filename unknown>:0 
  at MonoDevelop.IPhone.SelectSimulatorTargetHandler.Update (MonoDevelop.Components.Commands.CommandArrayInfo info) [0x00000] in <filename unknown>:0 
  at MonoDevelop.Components.Commands.CommandHandler.InternalUpdate (MonoDevelop.Components.Commands.CommandArrayInfo info) [0x00000] in <filename unknown>:0 
  at MonoDevelop.Components.Commands.CommandManager.DefaultUpdateCommandInfo (MonoDevelop.Components.Commands.ActionCommand cmd, MonoDevelop.Components.Commands.CommandInfo info) [0x00000] in <filename unknown>:0 
  at MonoDevelop.Components.Commands.CommandManager.GetCommandInfo (System.Object commandId, MonoDevelop.Components.Commands.CommandTargetRoute targetRoute) [0x00000] in <filename unknown>:0
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-11-30 06:48:13 UTC
Can you explain how we can reproduce this? What were you doing when it happened? Maybe you can create a screencast showing what you did (Jing [http://www.techsmith.com/jing.html] can be used for screencast for instance).
Comment 2 PJ 2013-11-19 17:05:15 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:35:34 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.