You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by su...@apache.org on 2017/12/04 19:22:12 UTC
[cordova-docs] branch master updated: Add automaticProvisioning to
iOS signing docs
This is an automated email from the ASF dual-hosted git repository.
surajpindoria pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cordova-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 178e307 Add automaticProvisioning to iOS signing docs
178e307 is described below
commit 178e307bca9b8c67c8170919c8efeaf39b3dc12a
Author: Darryl Pogue <da...@dpogue.ca>
AuthorDate: Tue Nov 14 21:19:57 2017 -0800
Add automaticProvisioning to iOS signing docs
Also tried to clean up the manual flags to indicate that automatic
signing is generally recommended, and you should only need to specify a
provisioningProfile UUID if you're using manual signing.
---
www/docs/en/dev/guide/platforms/ios/index.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/www/docs/en/dev/guide/platforms/ios/index.md b/www/docs/en/dev/guide/platforms/ios/index.md
index de400e6..2c6300a 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
{
--
To stop receiving notification emails like this one, please contact
['"commits@cordova.apache.org" <co...@cordova.apache.org>'].
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org