From 054b0bb70f293c06c305ef7a69b184be3f8daf4d Mon Sep 17 00:00:00 2001 From: sravan Date: Fri, 17 Jul 2026 13:30:11 +0530 Subject: [PATCH] ci(ios): remove ios_signing auto-fetch block so first build creates its own signing profile 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 --- codemagic.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/codemagic.yaml b/codemagic.yaml index c076647..9b2efe2 100644 --- a/codemagic.yaml +++ b/codemagic.yaml @@ -18,9 +18,11 @@ workflows: integrations: app_store_connect: BizGaze App Store Connect # ← must match the integration name you create environment: - ios_signing: - distribution_type: app_store - bundle_identifier: com.bizgaze.connect + # NOTE: we deliberately do NOT use an `ios_signing:` block here. That block makes Codemagic + # try to *fetch an existing* provisioning profile at build startup — it never creates one — so on + # 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: BUNDLE_ID: "com.bizgaze.connect" XCODE_WORKSPACE: "mobile/ios/App/App.xcworkspace"