Bug 10524 - Users must have XCode 4.4/4.5/4.6 installed
Summary: Users must have XCode 4.4/4.5/4.6 installed
Status: RESOLVED DUPLICATE of bug 10514
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 0.x Insider Preview
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jose Miguel Torres
Depends on:
Reported: 2013-02-21 09:25 UTC by Allie Miller
Modified: 2013-03-19 04:02 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 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-02-21 09:25:54 UTC
I did not get the VSAddIn running until I updated Xcode from 4.2.1 to the latest one 4.6. It failed on 'Checking a valid control connection on the server'. In the log I had [20-Feb-2013 22:39:15] Apple iOS SDK not found at '/Applications/Xcode.app'. Now everything is up and running.
Comment 1 Marek Habersack 2013-02-21 12:27:22 UTC
This is likely the same issue as bug #10514
Comment 2 Jose Miguel Torres 2013-03-19 04:02:28 UTC
This is because of the xcode-select print-path is not pointing to /Applications/Xcode.app. At #10514 there is a workaround. I am about to mark this issue as duplicated in order to follow up this issue in #10514

*** This bug has been marked as a duplicate of bug 10514 ***