Bug 11259 - Cannot Execute Xamarin.iOS projects
Summary: Cannot Execute Xamarin.iOS projects
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: 6.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-03-19 10:33 UTC by Allie Miller
Modified: 2013-03-25 18:03 UTC (History)
4 users (show)

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:

Description Allie Miller 2013-03-19 10:33:23 UTC
I'm getting a "cannot execute ....." error after a successful build for a monotouch application (using standard libraries).

I can run the application in the iPhone simulator fine, but the debugger won't connect.

Also tested with a new
"HelloWorld" project, and get the same error:

*Cannot execute "... path to bin files ..."*

Cannot find any further information in build errors / warnings, application
output etc...

This appears to be exactly the same as the following error:


Steps listed in the forum do not appear to work.

Using Xamarin 4.0.2 + all latest stable frameworks.

MonoDevelop: 4.0.2
Runtime: Mono 2.10.12 (mono-2-10/c9b270d)
Operating System: Mac OSX (Unix
Distributor: Xamarin
=== Xamarin Studio ===

Version 4.0.2 (build 18)
Installation UUID: 1b78c8cb-e7ba-4218-9e4c-d20322b4a2e1
Mono 2.10.12 (mono-2-10/c9b270d)
GTK 2.24.16
GTK# (
Package version: 210120000

=== Apple Developer Tools ===

Xcode 4.6.1 (2067)
Build 4H512

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.Android ===

Version: 4.6.0 (Starter Edition)
Android SDK: /Users/chrisleow/Library/Developer/Xamarin/android-sdk-mac_x86
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
Java SDK: /usr

=== Xamarin.iOS ===

Version: (Trial Edition)
Hash: 75565c0
Build date: 2013-08-03 13:37:04-0500

=== Build Information ===

Release ID: 400020018
Git revision: 2be11af94af70712cf550d12870275274b1ad399
Build date: 2013-03-08 07:22:12+0000
Xamarin addins: 11683a6440b38fa350cbe4d820f5cc6fee091295

=== Operating System ===

Mac OS X 10.8.3
Darwin Chriss-MacBook-Pro.local 12.3.0 Darwin Kernel Version 12.3.0
Sun Jan 6 22:37:10 PST 2013
root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64
Comment 2 Jeffrey Stedfast 2013-03-20 16:59:17 UTC
This looks like a Xamarin.iOS bug based on this forum thread: http://forums.xamarin.com/discussion/2452/cannot-execute-in-debug-mode-any-ios-project-even-hello-world#latest
Comment 3 Jeffrey Stedfast 2013-03-20 17:00:26 UTC
The second comment states that if he downgrades to Xamarin.iOS, then debugging works for him.

Xamarin.iOS (and newer?) fails.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2013-03-21 19:39:28 UTC
This looks like the same as http://forums.xamarin.com/discussion/comment/8565/#Comment_8565.

Probably because device-targeting merge made MD connect using port 10000 for the simulator (when we previously let the system chose any available port) - was that intentional, mhutch?

Potential fix is here: https://gist.github.com/rolfbjarne/c78abc10b909a6099c07
Comment 5 Mikayla Hutchinson [MSFT] 2013-03-21 21:53:42 UTC
This was not intentional.

IMO a better fix would be for IPhoneSettings.DebuggerPort to default to 0 though.
Comment 6 Rolf Bjarne Kvinge [MSFT] 2013-03-22 04:56:57 UTC
IPhoneSettings.DebuggerPort can't be 0 because it will break usb debugging - XS won't know which port to connect to on the device.
Comment 7 Jeffrey Stedfast 2013-03-25 18:03:17 UTC
this is fixed, btw