-
Notifications
You must be signed in to change notification settings - Fork 43
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update docs and remove dots in the and of annotations
- Loading branch information
1 parent
7ec9b92
commit c2540a2
Showing
46 changed files
with
393 additions
and
106 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
87 changes: 87 additions & 0 deletions
87
docs/app-store-connect/get-latest-testflight-build-number.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
|
|
||
| get-latest-testflight-build-number | ||
| ================================== | ||
|
|
||
|
|
||
| **Get latest Testflight build number for the given application** | ||
| ### Usage | ||
| ```bash | ||
| app-store-connect get-latest-testflight-build-number [-h] [--log-stream STREAM] [--no-color] [--version] [-s] [-v] | ||
| [--log-api-calls] | ||
| [--json] | ||
| [--issuer-id ISSUER_ID] | ||
| [--key-id KEY_IDENTIFIER] | ||
| [--private-key PRIVATE_KEY] | ||
| [--certificates-dir CERTIFICATES_DIRECTORY] | ||
| [--profiles-dir PROFILES_DIRECTORY] | ||
| [--pre-release-version PRE_RELEASE_VERSION] | ||
| APPLICATION_ID | ||
| ``` | ||
| ### Required arguments for action `get-latest-testflight-build-number` | ||
|
|
||
| ##### `APPLICATION_ID` | ||
|
|
||
|
|
||
| Application Apple ID | ||
| ### Optional arguments for action `get-latest-testflight-build-number` | ||
|
|
||
| ##### `--pre-release-version=PRE_RELEASE_VERSION` | ||
|
|
||
|
|
||
| Pre-release version of your application | ||
| ### Optional arguments for command `app-store-connect` | ||
|
|
||
| ##### `--log-api-calls` | ||
|
|
||
|
|
||
| Turn on logging for App Store Connect API HTTP requests | ||
| ##### `--json` | ||
|
|
||
|
|
||
| Whether to show the resource in JSON format | ||
| ##### `--issuer-id=ISSUER_ID` | ||
|
|
||
|
|
||
| App Store Connect API Key Issuer ID. Identifies the issuer who created the authentication token. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_ISSUER_ID`. Alternatively to entering` ISSUER_ID `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--key-id=KEY_IDENTIFIER` | ||
|
|
||
|
|
||
| App Store Connect API Key ID. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_KEY_IDENTIFIER`. Alternatively to entering` KEY_IDENTIFIER `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--private-key=PRIVATE_KEY` | ||
|
|
||
|
|
||
| App Store Connect API private key. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_PRIVATE_KEY`. Alternatively to entering` PRIVATE_KEY `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--certificates-dir=CERTIFICATES_DIRECTORY` | ||
|
|
||
|
|
||
| Directory where the code signing certificates will be saved. Default: `$HOME/Library/MobileDevice/Certificates` | ||
| ##### `--profiles-dir=PROFILES_DIRECTORY` | ||
|
|
||
|
|
||
| Directory where the provisioning profiles will be saved. Default: `$HOME/Library/MobileDevice/Provisioning Profiles` | ||
| ### Common options | ||
|
|
||
| ##### `-h, --help` | ||
|
|
||
|
|
||
| show this help message and exit | ||
| ##### `--log-stream=stderr | stdout` | ||
|
|
||
|
|
||
| Log output stream. Default `stderr` | ||
| ##### `--no-color` | ||
|
|
||
|
|
||
| Do not use ANSI colors to format terminal output | ||
| ##### `--version` | ||
|
|
||
|
|
||
| Show tool version and exit | ||
| ##### `-s, --silent` | ||
|
|
||
|
|
||
| Disable log output for commands | ||
| ##### `-v, --verbose` | ||
|
|
||
|
|
||
| Enable verbose logging for commands |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
|
|
||
| get-testflight-build | ||
| ==================== | ||
|
|
||
|
|
||
| **Get specified Build from Apple Developer portal** | ||
| ### Usage | ||
| ```bash | ||
| app-store-connect get-testflight-build [-h] [--log-stream STREAM] [--no-color] [--version] [-s] [-v] | ||
| [--log-api-calls] | ||
| [--json] | ||
| [--issuer-id ISSUER_ID] | ||
| [--key-id KEY_IDENTIFIER] | ||
| [--private-key PRIVATE_KEY] | ||
| [--certificates-dir CERTIFICATES_DIRECTORY] | ||
| [--profiles-dir PROFILES_DIRECTORY] | ||
| [--build-id BUILD_ID] | ||
| ``` | ||
| ### Optional arguments for action `get-testflight-build` | ||
|
|
||
| ##### `--build-id=BUILD_ID` | ||
|
|
||
|
|
||
| Build id | ||
| ### Optional arguments for command `app-store-connect` | ||
|
|
||
| ##### `--log-api-calls` | ||
|
|
||
|
|
||
| Turn on logging for App Store Connect API HTTP requests | ||
| ##### `--json` | ||
|
|
||
|
|
||
| Whether to show the resource in JSON format | ||
| ##### `--issuer-id=ISSUER_ID` | ||
|
|
||
|
|
||
| App Store Connect API Key Issuer ID. Identifies the issuer who created the authentication token. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_ISSUER_ID`. Alternatively to entering` ISSUER_ID `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--key-id=KEY_IDENTIFIER` | ||
|
|
||
|
|
||
| App Store Connect API Key ID. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_KEY_IDENTIFIER`. Alternatively to entering` KEY_IDENTIFIER `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--private-key=PRIVATE_KEY` | ||
|
|
||
|
|
||
| App Store Connect API private key. Learn more at https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api. If not given, the value will be checked from environment variable `APP_STORE_CONNECT_PRIVATE_KEY`. Alternatively to entering` PRIVATE_KEY `in plaintext, it may also be specified using a `@env:` prefix followed by a environment variable name, or `@file:` prefix followed by a path to the file containing the value. Example: `@env:<variable>` uses the value in the environment variable named `<variable>`, and `@file:<file_path>` uses the value from file at `<file_path>`. | ||
| ##### `--certificates-dir=CERTIFICATES_DIRECTORY` | ||
|
|
||
|
|
||
| Directory where the code signing certificates will be saved. Default: `$HOME/Library/MobileDevice/Certificates` | ||
| ##### `--profiles-dir=PROFILES_DIRECTORY` | ||
|
|
||
|
|
||
| Directory where the provisioning profiles will be saved. Default: `$HOME/Library/MobileDevice/Provisioning Profiles` | ||
| ### Common options | ||
|
|
||
| ##### `-h, --help` | ||
|
|
||
|
|
||
| show this help message and exit | ||
| ##### `--log-stream=stderr | stdout` | ||
|
|
||
|
|
||
| Log output stream. Default `stderr` | ||
| ##### `--no-color` | ||
|
|
||
|
|
||
| Do not use ANSI colors to format terminal output | ||
| ##### `--version` | ||
|
|
||
|
|
||
| Show tool version and exit | ||
| ##### `-s, --silent` | ||
|
|
||
|
|
||
| Disable log output for commands | ||
| ##### `-v, --verbose` | ||
|
|
||
|
|
||
| Enable verbose logging for commands |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.