Status: Migrating from 4.5.1 to 4.5.2 + selected target device + command line tools update.
Status: Migrating from 4.5.1 to 4.5.2 + selected target device + command line tools update.
- Subject: Status: Migrating from 4.5.1 to 4.5.2 + selected target device + command line tools update.
- From: Alex Zavatone <email@hidden>
- Date: Fri, 02 Nov 2012 18:04:39 -0400
Details follow:
Took our install of 4.5.1 in a 13" MBP with Mountain Lion and made sure that the command line tools was installed.
Created a new user called Xcode452, signed in under that user and ran the 4.5.2 installer.
Made sure that in Preferences, all the Documentation and Components were set to install and that they were completed. There was no button next to the command line tools that indicated that they could be or will be updated.
NOTE: there is no indication that the command line tools are of any version what so ever and while all the docs and components installed, there was no information stating the version of the command line tools, or if they are being updated or not at this point. This changes later.
Created a new iOS project of a single view controller, added a table to it and built to the Simulator under iPhone.
Quit and relaunched by double clicking on the project.
Upon relaunching the project still retained the selected preference to launch as an iPhone app in the Simulator.
Plugged in the iPod Touch with iOS 6.0. Signed in using my Enterprise account and had provisioning profiles installed automatically (really nice and fast with appropriate GUI). Was able to set the device to be used for Development, but was unable to deploy to it since "there are no valid public/private keys". No idea why, but that is a separate issue.
Quit and relaunched Xcode and the project still wanted to launch to the iPhone Simulator as had been initially selected.
So, Matt and Tom, I'm not seeing your problem in my simple test case.
Do either of you have a simple case that I can test?
Thoughts:
Could this be a file permissions error? Where whichever file stores these settings can not be written to?
Note:
At this time, the Preferences GUI for the command line tools still displays "Installed", to the right of the component.
As I am walking back to write this email, Xcode displays the dialog of "Install Updates" mentioning that there are updates ready for the command line tools.
Clicked the Install button and they have successfully downloaded and installed. 115.6 MB
Don't know how, why or when this gets triggered, but Fons, this update check might automatically kick in when Xcode is done installing the current documentation and components and has idle time. At least in my case, it happened after every other install and at an idle moment.
Summary:
1. I am not seeing the Deployment target changing on a relaunch as Matt and Tom have seen.
2. Command line tools were able to be installed, but the GUI for this component is completely uninformative as to when/if they can be and what the installed version the current command line tools are.
Follow up:
I'd like to take another Mac or another user folder, install a fresh copy of Xcode 4.5.2 and make sure that upon signing in from a fresh starting state, I'm able to deploy directly to a device from a clean install.
Matt/Tom, if you have a sample file, I'd be glad to test on my configuration.
Fons, hopefully, if there are downloads finishing for components, the command line tools will update after they are done. Does anyone know what triggers a check for an update of the command line tools?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden