This is an automated email from the ASF dual-hosted git repository.

erisu 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 18f1dbaabb docs(ios): Cloud Distribution Signing flags (#1280)
18f1dbaabb is described below

commit 18f1dbaabb0e108a3fa4e9b1b739213d11d2b577
Author: Darryl Pogue <[email protected]>
AuthorDate: Mon Apr 24 20:38:39 2023 -0700

    docs(ios): Cloud Distribution Signing flags (#1280)
---
 www/docs/en/dev/guide/platforms/ios/index.md | 33 +++++++++++++---------------
 1 file changed, 15 insertions(+), 18 deletions(-)

diff --git a/www/docs/en/dev/guide/platforms/ios/index.md 
b/www/docs/en/dev/guide/platforms/ios/index.md
index e49db69745..15cc45a5a9 100644
--- a/www/docs/en/dev/guide/platforms/ios/index.md
+++ b/www/docs/en/dev/guide/platforms/ios/index.md
@@ -163,13 +163,17 @@ and the [App Distribution 
Workflows](https://developer.apple.com/library/prerele
 
 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`.
-| 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.
-| Automatic Provisioning   | `--automaticProvisioning`| (Optional) Enable to 
allow Xcode to automatically manage provisioning profiles. Valid options are 
`false` (the default) and `true`.
+| 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`.
+| 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.
+| Automatic Provisioning       | `--automaticProvisioning`     | (Optional) 
Enable to allow Xcode to automatically manage provisioning profiles. Valid 
options are `false` (the default) and `true`.
+| Authentication Key Path      | `--authenticationKeyPath`     | (Optional) 
The path to an [App Store Connect 
API](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)
 p8 key file, for automatic distribution signing.
+| Authentication Key ID        | `--authenticationKeyID`       | (Optional) 
The key ID for the App Store Connect API key file, for automatic distribution 
signing.
+| Authentication Key Issuer ID | `--authenticationKeyIssuerID` | (Optional) 
The issuer ID value for the App Store Connect API credentials,for automatic 
distribution signing.
+
 
 ### Using build.json
 
@@ -186,23 +190,16 @@ For automatic signing, where provisioning profiles are 
managed automatically by
             "codeSignIdentity": "iPhone Developer",
             "developmentTeam": "FG35JLLMXX4A",
             "packageType": "development",
-            "automaticProvisioning": true,
-            "buildFlag": [
-                "EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
-                "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
-                "LD_RUNPATH_SEARCH_PATHS = \"@executable_path/Frameworks\""
-            ]
+            "automaticProvisioning": true
         },
         "release": {
             "codeSignIdentity": "iPhone Developer",
             "developmentTeam": "FG35JLLMXX4A",
             "packageType": "app-store",
             "automaticProvisioning": true,
-            "buildFlag": [
-                "EMBEDDED_CONTENT_CONTAINS_SWIFT = YES",
-                "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES=NO",
-                "LD_RUNPATH_SEARCH_PATHS = \"@executable_path/Frameworks\""
-            ]
+            "authenticationKeyPath": "/path/to/AuthKey_D383SF739.p8",
+            "authenticationKeyID": "D383SF739",
+            "authenticationKeyIssuerID": "6053b7fe-68a8-4acb-89be-165aa6465141"
         }
     }
 }


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

Reply via email to