fix: use App Store Connect API key for code signing in CI#3
Merged
Conversation
…pp Store Connect signing in CI
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The build was failing with:
The App Store Connect API key was only being used for the upload step, but the build step was trying to sign without any authentication — macOS runners have no Apple accounts pre-added.
Solution
Pass the App Store Connect API key to both signing functions so Fastlane can automatically create/manage provisioning profiles via the API:
This is the standard approach for CI-only App Store signing when using App Store Connect API keys (no Apple ID needed).