[TIMOB-10852] iOS: tooling - Studio correctly passes iOS compile target, but scripts use latest iOS SDK regardless of setting
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2012-10-11T00:10:42.000+0000 |
Affected Version/s | Release 2.1.2, Release 2.1.3 |
Fix Version/s | 2012 Sprint 21 JS, 2012 Sprint 21 |
Components | Tooling |
Labels | core |
Reporter | Eric Merriman |
Assignee | Ingo Muschenetz |
Created | 2012-09-11T15:45:14.000+0000 |
Updated | 2013-03-27T22:31:55.000+0000 |
Description
While testing iOS and Xcode 4.5 we saw a failure trying to compile with iOS 5 target. This failure was identical to the failure seen when trying to compile with an iOS 6 compile target. After closer examination, we determined that no matter what the setting was, the build would always target the latest installed SDK (as interpreted by Xcode).
e.g. Setting to iOS 5.0 when 5.0, 5.1 and iOS 6 are options, iOS 6 is used.
I have verified that Studio is sending the correct arguments:
"/Users/emerriman/Library/Application Support/Titanium/mobilesdk/osx/2.1.1.GA/iphone/builder.py" "install" "5.0" "/Users/emerriman/212Workspace/ericDevTest" "com.appcelerator.devtest" "ericDevTest" "25360090-4A84-4F2A-8415-B53E250EAB05" "Eric Merriman (9JUJ8DJW9G)" "universal"
But the build process still reports:
[INFO] Titanium SDK version: 2.1.3 (09/07/12 16:31 9699f0a)
[INFO] iPhone Device family: universal
[INFO] iPhone SDK version: 6.0
[INFO] Performing full rebuild. This will take a little bit. Hold tight...
This is not a regression. Occurs in 2.1.2GA and 2.1.1GA.
Occurs with Xcode 4.4.1 and Xcode 4.5
Eric, what do you see if you do
in a Terminal session? For me, with Xcode 4.5 installed, I get:
So if you're doing "install" (to a device),indeed there is only one available and so it grabs it no matter what you selected. So in the selection list in Titanium Studio, when user has chosen to build for device, I guess we shouldn't show the simulator-only SDKs. Sound right? (This would also require a change to Studio.)
We should investigate for the new CLI to see if this is still an issue and how we handle it.
This is fixed in the new CLI.
This won't be fixed because the old CLI is deprecated and the new CLI supports this correctly.