[TIMOB-16181] Appcelerator Studio was not able to locate the correct Simulator Version
GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Cannot Reproduce |
Resolution Date | 2014-01-15T20:24:10.000+0000 |
Affected Version/s | Release 3.2.0 |
Fix Version/s | n/a |
Components | CLI |
Labels | n/a |
Reporter | Radamantis Torres-Lechuga |
Assignee | Chris Barber |
Created | 2014-01-14T00:00:53.000+0000 |
Updated | 2014-06-19T12:43:38.000+0000 |
Description
Issue
When trying to build a project for iOS from within Appcelerator Studio, you consistently get an error stating that you require SDK 7.0.3 for iOS.
Problem
Proper version of Xcode is not getting detected
Validate
Make sure you have the latest version of Xcode (v 5.0.2)
- from the project root directory (E.G. ~/Users/yourusername/Appcelerator_Studio_Workspace/HelloWorld) run the following command line:
titanium build --platform ios --ios-version 7.0.3
- you should see an error about locating a configuration file
Fix
force a redirection of Xcode by Titanium using the following command from terminal
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
Attachments
Moving this to TIMOB since Studio relies on the CLI to return the right Xcode path. Also the fact that running the build command from command line produces an error indicates CLI is using the incorrect path.
Attaching screenshot of the error about the config.json The archive was not in the directory but we were able to read the config using ti config command, we created an empty file in the correct path and then ti config failed, after that, we created a simple config.json file
This ticket is missing critical information such as the output from "ti info -t ios". Please include that in future. If Xcode is really located at /Applications/Xcode.app, then the CLI will find it. Regarding the screenshot, as the error indicates, the Titanium CLI config cannot be opened. This is most likely because you ran Titanium as sudo and now config.json is owned by root. To fix it, run:
sudo chown
whoami~/.titanium/config.json
. I'm resolving this as cannot reproduce. Feel free to re-open if a reproducible test case can be defined.