[ 
https://issues.jenkins-ci.org/browse/JENKINS-14028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Longhurst updated JENKINS-14028:
--------------------------------------

    Description: 
I noticed that specifying a path to my .mobileprovision in the XCodeBuild 
configuration for a project, whilst using the  "Build IPA" setting doesn't 
actually embed that provision in the final IPA file.

On the xcrun command line, if you specify --embed /path/to/my.mobileprovision, 
the command doesn't seem to actually embed the provision unless you also 
specify --sign "iPhone Distribution: My Name" at the same time.  When you 
specify --sign, you get a verbose message like so:

{noformat}
### Embedding '/Jenkins/workspace/my-ios-project/my.mobileprovision'
{noformat}

Making use of the additional codeSigningIdentity parameter (added in the latest 
Github sourcr), adding the following lines to XCodeBuilder.java:468 in the 
1.3.2-SNAPSHOT src (just after the --embed output) fix the problem:

{code}
if (!StringUtils.isEmpty(codeSigningIdentity)) {                   
   packageCommandLine.add("--sign");
   packageCommandLine.add(codeSigningIdentity);
}
{code}

  was:
I noticed that specifying a path to my .mobileprovision in the XCodeBuild 
configuration for a project, whilst using the  "Build IPA" setting doesn't 
actually embed that provision in the final IPA file.

On the xcrun command line, if you specify --embed /path/to/my.mobileprovision, 
the command doesn't seem to actually embed the provision unless you also 
specify --sign "iPhone Distribution: My Name" at the same time.  When you 
specify --sign, you get a verbose message like so:

### Embedding '/Jenkins/workspace/my-ios-project/my.mobileprovision'

Making use of the additional codeSigningIdentity parameter (added in the latest 
Github sourcr), adding the following lines to XCodeBuilder.java:468 in the 
1.3.2-SNAPSHOT src (just after the --embed output) fix the problem:

if (!StringUtils.isEmpty(codeSigningIdentity)) {                   
   packageCommandLine.add("--sign");
   packageCommandLine.add(codeSigningIdentity);
}

    
> Embedding .mobileprovision for IPA build doesn't work XCode 4.2 (4C199)
> -----------------------------------------------------------------------
>
>                 Key: JENKINS-14028
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-14028
>             Project: Jenkins
>          Issue Type: Bug
>          Components: xcode
>    Affects Versions: current
>         Environment: XCode 4.2 (4C199)
> MacOS 10.6.8 (Snow Leopard)
> Jenkins 1.467
>            Reporter: Steve Longhurst
>
> I noticed that specifying a path to my .mobileprovision in the XCodeBuild 
> configuration for a project, whilst using the  "Build IPA" setting doesn't 
> actually embed that provision in the final IPA file.
> On the xcrun command line, if you specify --embed 
> /path/to/my.mobileprovision, the command doesn't seem to actually embed the 
> provision unless you also specify --sign "iPhone Distribution: My Name" at 
> the same time.  When you specify --sign, you get a verbose message like so:
> {noformat}
> ### Embedding '/Jenkins/workspace/my-ios-project/my.mobileprovision'
> {noformat}
> Making use of the additional codeSigningIdentity parameter (added in the 
> latest Github sourcr), adding the following lines to XCodeBuilder.java:468 in 
> the 1.3.2-SNAPSHOT src (just after the --embed output) fix the problem:
> {code}
> if (!StringUtils.isEmpty(codeSigningIdentity)) {                   
>    packageCommandLine.add("--sign");
>    packageCommandLine.add(codeSigningIdentity);
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to