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.
I've FINALLY managed to reproduce this enough to get the errors out.
MD 2.6 B2
this happens when running in the simulator, and possibly on the device too. The error (once the app has built) is below.
It doesn't happen every time. More over, it doesn't happen on every _project_. But project A will work for a while, then it'll top, but B might start working for a while... it's very very odd.
Running works fine. I just can't debug. Sometimes.
I'm going to submit this, and reboot, and see if it goes away. Expect more comments below.
Cannot execute "/Users/nic/code/git/mobileagent/bin/iPhoneSimulator/Debug/DeadDrop.exe". Could not load type 'MonoDevelop.Debugger.Soft.IPhone.IPhoneDebuggerStartInfo' from assembly 'MonoDevelop.Debugger.Soft.IPhone, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.
System.TypeLoadException: Could not load type 'MonoDevelop.Debugger.Soft.IPhone.IPhoneDebuggerStartInfo' from assembly 'MonoDevelop.Debugger.Soft.IPhone, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'.
at MonoDevelop.Debugger.DebuggerEngine.CreateDebuggerStartInfo (MonoDevelop.Core.Execution.ExecutionCommand cmd) [0x00006] in /Users/michael/Mono/md-2-5-91/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebuggerEngine.cs:82
at MonoDevelop.Debugger.DebuggingService.InternalRun (MonoDevelop.Core.Execution.ExecutionCommand cmd, MonoDevelop.Debugger.DebuggerEngine factory, IConsole c) [0x0003a] in /Users/michael/Mono/md-2-5-91/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebuggingService.cs:483
at MonoDevelop.Debugger.DebugExecutionHandler.Execute (MonoDevelop.Core.Execution.ExecutionCommand command, IConsole console) [0x00000] in /Users/michael/Mono/md-2-5-91/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebugExecutionHandlerFactory.cs:70
at MonoDevelop.Debugger.DebugExecutionHandlerFactory.Execute (MonoDevelop.Core.Execution.ExecutionCommand command, IConsole console) [0x00015] in /Users/michael/Mono/md-2-5-91/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/DebugExecutionHandlerFactory.cs:52
at MonoDevelop.Projects.DotNetProject.DoExecute (IProgressMonitor monitor, MonoDevelop.Projects.ExecutionContext context, MonoDevelop.Projects.ConfigurationSelector configuration) [0x000b2] in /Users/michael/Mono/md-2-5-91/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/DotNetProject.cs:1138
Nope, I can reproduce it all the time now. Very strange. All the projects worked this morning, and now none of them do, even after a reboot.
Is there some debug thing I can turn on in MD to see whats going on under the hood?
I upgraded to 2.6b3 and MT 220.127.116.11 and it appears to work.
Of course, it's done this before. Is there anything I can do to get more debug info out?
This might be due to having an incompatible version of the MonoTouch add-in. Feel free to reopen if you get this error again with b3.