Sravan/BizGaze_Remote
0
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ci(ios): remove ios_signing auto-fetch block so first build creates its own signing profile

Browse Source 
The environment.ios_signing block makes Codemagic fetch an EXISTING profile at
build init and fails with 'No matching profiles found' on a brand-new app. The
'Set up code signing' script already creates the cert+profile via
fetch-signing-files --create, so the block was both redundant and blocking.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Sravan
2026-07-17 13:30:11 +05:30
parent c18e55b5ec
commit 054b0bb70f
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
codemagic.yaml
+5 -3
View File
@@ -18,9 +18,11 @@ workflows:
integrations: integrations:
app_store_connect: BizGaze App Store Connect # ← must match the integration name you create app_store_connect: BizGaze App Store Connect # ← must match the integration name you create
environment: environment:
ios_signing: # NOTE: we deliberately do NOT use an `ios_signing:` block here. That block makes Codemagic
distribution_type: app_store # try to *fetch an existing* provisioning profile at build startup — it never creates one — so on
bundle_identifier: com.bizgaze.connect # a brand-new app it fails init with "No matching profiles found …". Instead the "Set up code
# signing" script below runs `fetch-signing-files … --create`, which creates the distribution
# certificate + profile on first run, then `xcode-project use-profiles` wires them into the project.
vars: vars:
BUNDLE_ID: "com.bizgaze.connect" BUNDLE_ID: "com.bizgaze.connect"
XCODE_WORKSPACE: "mobile/ios/App/App.xcworkspace" XCODE_WORKSPACE: "mobile/ios/App/App.xcworkspace"