[TIMOB-16045] CLI: iOS: Device builds from Xcode fail unless a developer cert and provisioning profile is selected
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-12-18T23:27:57.000+0000 |
| Affected Version/s | Release 3.2.0 |
| Fix Version/s | 2013 Sprint 26, 2013 Sprint 26 Core, Release 3.2.0, Release 3.3.0 |
| Components | CLI, iOS |
| Labels | module_xcodebuild, qe-closed-3.2.0, qe-testadded |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2013-12-18T21:03:22.000+0000 |
| Updated | 2014-07-31T09:46:23.000+0000 |
Description
If you create a project and build for iOS, then open the generated Xcode project and build for device, the build fails unless you explicitly select a developer cert and provisioning profile from the build settings tab.
The CLI doesn't actually NEED either of these, so it should be safe to make them not required.
Here's the original Q&A question: http://developer.appcelerator.com/question/160611/xcode-compile-error-320-sdk-titanium-320-and-osx-1091.
Master pull request: https://github.com/appcelerator/titanium_mobile/pull/5147 3.2.x pull request: https://github.com/appcelerator/titanium_mobile/pull/5148
Closing ticket as fixed. Verified I was able to install an app (both Alloy and Classic) directly from Xcode to an iOS device without selecting a developer cert and provisioning profile in the Build Settings. Tested on: Appcelerator Studio, build: 3.2.0.201312181652 SDK build: 3.2.0.v20131218153242 CLI: 3.2.0-cr3 Alloy: 1.3.0-cr2 Xcode: 5.0.2 Devices: iphone 5 (6.1.3), iphone 5s (7.0.2)