Bug 14219 - Xamarin Studio could not communicate with Xcode
Summary: Xamarin Studio could not communicate with Xcode
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-08-23 20:45 UTC by Tim Uy
Modified: 2015-03-06 14:49 UTC (History)
1 user (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 ANSWERED

Description Tim Uy 2013-08-23 20:45:41 UTC
I see that this bug is also in 5440, but for MD. I just switched from MD to "Xamarin Studio" seeing the changes. However, when I click on the xib file in a new Xamarin Mac project I get the "Xamarin Studio could not communicate with Xcode. Any help would be much appreciated. I need to get this up and running.
Comment 1 Jeffrey Stedfast 2013-08-23 22:26:31 UTC
try starting Xcode manually. You probably need to fill in some info in Xcode or something (which prevents Xamarin Studio from being able to communicate with it)
Comment 2 Jeffrey Stedfast 2015-03-06 14:49:29 UTC
I think it's safe to close this now.