From 3ecb229b6a1f3099d15d05bd07e218202a791d64 Mon Sep 17 00:00:00 2001 From: Luke Roberts Date: Tue, 13 Jun 2023 22:35:14 +0100 Subject: [PATCH] Update "Installing an Apple certificate on macOS runners for Xcode development" to include macOS build target note (#37817) Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> --- ...le-certificate-on-macos-runners-for-xcode-development.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 837fd64cb4..3174ae0108 100644 --- a/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -116,6 +116,12 @@ jobs: ... ``` +{% note %} + +**Note:** For iOS build targets, your provisioning profile should have the extension `.mobileprovision`. For macOS build targets, the extension should be `.provisionprofile`. The example workflow above should be updated to reflect your target platform. + +{% endnote %} + ## Required clean-up on self-hosted runners {% data variables.product.prodname_dotcom %}-hosted runners are isolated virtual machines that are automatically destroyed at the end of the job execution. This means that the certificates and provisioning profile used on the runner during the job will be destroyed with the runner when the job is completed.