[ 
https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177369#comment-14177369
 ] 

ASF subversion and git services commented on CB-7818:
-----------------------------------------------------

Commit c0db6382af2e2570be139d584f553ca5c046a941 in cordova-ios's branch 
refs/heads/master from [~SidneyS]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=c0db638 ]

CB-7818 - CLI builds ignore Distribution certificates (closes #114)

Fixed build / xcconfig defaults for CI environments. "cordova build -…
…-device --release" now builds using the "iPhone Distribution"-type profile, as 
opposed to the default "cordova build --device", using the default "iPhone 
Developer"-type profile.

Re-added build.xcconfig as shared .xcconfig for legacy compatibility. 
Implemented Configuration-level .xcconfig selection via inheritance. Added ASF 
comment section, short documentation.

Signed-off-by: Shazron Abdullah <[email protected]>


> CLI builds ignore Distribution certificates
> -------------------------------------------
>
>                 Key: CB-7818
>                 URL: https://issues.apache.org/jira/browse/CB-7818
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 3.5.0
>            Reporter: SidneyS
>            Assignee: Shazron Abdullah
>             Fix For: 3.7.0
>
>
> Hi, 
> currently, cordova build --release --device yields in device builds using a 
> default "iOS Development"-type Signing Identity. Intuitively, using "release" 
> in conjunction with "device" should try to leverage a local "iOS 
> Distribution"-type identity to enable CLI adhoc/inhouse-builds without 
> patching xcconfig/xcodeproject files on runtime, or re-signing the created 
> binary after using the default build process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to