[TIMOB-16894] CLI should accept production value for '--deploy-type' argument while packaging iOS app
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-05-07T23:34:42.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2014 Sprint 09, 2014 Sprint 09 Tooling, Release 3.3.0 |
| Components | CLI |
| Labels | module_package, qe-closed-3.3.0, qe-testadded |
| Reporter | Praveen Innamuri |
| Assignee | Chris Barber |
| Created | 2014-04-29T22:56:47.000+0000 |
| Updated | 2014-07-28T19:32:59.000+0000 |
Description
CLI accepts '--deploy-type' value as production for MobileWeb for packaging the app. However, it doesn't accept 'production' for --deploy-type argument while packaging Android and iOS apps.
We will not allow the deploy type to be changed for distribution builds. Mobile Web is in the wrong here. Mobile Web should have targets that dictate the deploy type. The build configuration feature is the correct way to allow users to override the deploy type.
My bad, the title of this ticket was changed. I see the bug.
Titanium SDK master pull request: https://github.com/appcelerator/titanium_mobile/pull/5662 To test, run
ti build -p ios -T dist-appstore --deploy-type production.Using the above command
verified CLI accepting production value for '--deploy-type' argument while packaging iOS app Used environment: Mac osx 10.9.2 Mavericks Appcelerator Studio, build: 3.3.0.201405011408 Titanium SDK, build: 3.3.0.v20140507163312 Node.JS Version: v0.10.13 NPM Version: 1.3.2 acs@1.0.14 alloy@1.4.0-dev npm@1.3.2 titanium@3.3.0-dev titanium-code-processor@1.1.1 Xcode 5.1.1