[
https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277313#comment-16277313
]
ASF GitHub Bot commented on CB-13523:
-------------------------------------
surajpindoria closed pull request #762: CB-13523: Add automaticProvisioning to
iOS signing docs
URL: https://github.com/apache/cordova-docs/pull/762
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/www/docs/en/dev/guide/platforms/ios/index.md
b/www/docs/en/dev/guide/platforms/ios/index.md
index de400e6fe..2c6300a77 100644
--- a/www/docs/en/dev/guide/platforms/ios/index.md
+++ b/www/docs/en/dev/guide/platforms/ios/index.md
@@ -160,10 +160,11 @@ To sign an app, you need the following parameters:
| Parameter | Flag | Description
|--------------------------|--------------------------|-----------------------------------
| Code Sign Identity | `--codeSignIdentity` | Code signing identity
to use for signing. It can be created with Xcode and added to your keychain.
Starting with Xcode 8 you should use `--codeSignIdentity="iPhone Developer"`
both for `debug` and `release`.
-| Provisioning Profile | `--provisioningProfile` | GUID of the
provisioning profile to be used for signing. It is copied here on your Mac:
```~/Library/MobileDevice/Provisioning\ Profiles/```. Opening it in a text
editor, you can find the GUID which needs to be specified here.
-| Code Sign Resource Rules | `--codesignResourceRules`| (Optional) Used to
control which files in a bundle should be sealed by a code signature. For more
details, read [The OS X Code Signing In Depth
article](https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG206)
-| Development Team | `--developmentTeam` | This is new for Xcode
8. The development team ([Team
ID](https://developer.apple.com/account/#/membership/)) to use for code
signing. You would use this setting and a simplified Code Sign Identity (i.e.
just 'iPhone Developer') to sign your apps, you do not need to provide a
Provisioning Profile.
+| Development Team | `--developmentTeam` | The development team
([Team ID](https://developer.apple.com/account/#/membership/)) to use for code
signing. You would use this setting and a simplified Code Sign Identity (i.e.
just 'iPhone Developer') to sign your apps, you do not need to provide a
Provisioning Profile.
| Packaging Type | `--packageType` | This will determine
what type of build is generated by Xcode. Valid options are `development` (the
default), `enterprise`, `ad-hoc`, and `app-store`.
+| Provisioning Profile | `--provisioningProfile` | (Optional) GUID of the
provisioning profile to be used for manual signing. It is copied here on your
Mac: ```~/Library/MobileDevice/Provisioning\ Profiles/```. Opening it in a text
editor, you can find the GUID which needs to be specified here if using manual
signing.
+| Code Sign Resource Rules | `--codesignResourceRules`| (Optional) Used to
control which files in a bundle should be sealed by a code signature. For more
details, read [The OS X Code Signing In Depth
article](https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG206)
+| Automatic Provisioning | `--automaticProvisioning`| (Optional) Enable to
allow Xcode to automatically manage provisioning profiles. Valid options are
`false` (the default) and `true`.
### Using build.json
@@ -171,7 +172,7 @@ Alternatively, you could specify them in a build
configuration file (`build.json
using the `--buildConfig` argument to the same commands. Here's a sample of a
build configuration file:
-Xcode 8 and iOS 10:
+For automatic signing, where provisioning profiles are managed automatically
by Xcode (recommended):
```json
{
@@ -180,6 +181,7 @@ Xcode 8 and iOS 10:
"codeSignIdentity": "iPhone Developer",
"developmentTeam": "FG35JLLMXX4A",
"packageType": "development",
+ "automaticProvisioning": true,
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
@@ -190,6 +192,7 @@ Xcode 8 and iOS 10:
"codeSignIdentity": "iPhone Developer",
"developmentTeam": "FG35JLLMXX4A",
"packageType": "app-store",
+ "automaticProvisioning": true,
"buildFlag": [
"EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
"ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
@@ -200,7 +203,7 @@ Xcode 8 and iOS 10:
}
```
-Earlier versions:
+For manual signing, specifying the provisioning profiles by UUID:
```json
{
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add build config option to enable Xcode automatic provisioning
> --------------------------------------------------------------
>
> Key: CB-13523
> URL: https://issues.apache.org/jira/browse/CB-13523
> Project: Apache Cordova
> Issue Type: Improvement
> Components: cordova-ios
> Environment: Xcode 9
> Cordova-iOS 4.5.3
> Reporter: Darryl Pogue
> Assignee: Darryl Pogue
> Fix For: [email protected]
>
>
> Xcode 9 made more changes to how provisioning works for apps, particularly
> around manual vs automatic signing.
> The changes required to support manual signing of release builds was
> implemented as part of CB-13315.
> In order for automatic signing to work, we need to pass an additional flag to
> xcodebuild to allow Xcode to manage automatically updating provisioning
> profiles as needed. I want to keep this being a build config option because
> many people may not want to grant Xcode such power by default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
