exportArchive "Runner.app" requires a provisioning profile despite correct setup (pubspec.yaml, Info.plist, YAML)

[soury]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

1. Set correct bundle_identifier in pubspec.yaml and ios/Runner/Info.plist
2. Set up iOS signing in codemagic.yaml using both:
   • Method 1: ios_signing.distribution_type: app_store + bundle_identifier
   • Method 2: ios_signing.certificates and ios_signing.provisioning_profiles
3. Ensure Apple Developer integration (CodemagicKey) is active
4. Set export options via xcode-project use-profiles --custom-export-options
5. Run flutter build ipa --release

Expected results

The app should be successfully archived and exported as an IPA file, using the correct provisioning profile.

Actual results

Build fails with:

❗ App Settings Validation:

• Version Number: Missing
• Build Number: Missing
• Display Name: Missing
  (But these values are present in pubspec.yaml and Info.plist)

❗ exportArchive "Runner.app" requires a provisioning profile.

This happens even when using correct bundle identifier and profile name, both with automatic and manual signing methods.

Related discussion was marked “resolved on Discord” but no solution was posted:
https://github.com/orgs/codemagic-ci-cd/discussions/2489

Build id (optional)

68c84026db4b407fc18bf4b4

[dam-ease]

Hello @soury,
Can you please try using the script below in your Build iOS IPA step instead:

      - name: Flutter build ipa
        script: | 
          flutter build ipa --release \
            --build-name=1.0.0 \
            --build-number=$PROJECT_BUILD_NUMBER \
            --export-options-plist=/Users/builder/export_options.plist

Kindly try this out and share how this goes on your end.

[dam-ease]

In your ios /Runner/Info.plist file, can you please double-check to confirm that it contains the following:

• CFBundleVersion and set its key to $(FLUTTER_BUILD_NUMBER)
• CFBundleShortVersionString and set its key to $(FLUTTER_BUILD_NAME)

As below:

	<key>CFBundleShortVersionString</key>
	<string>$(FLUTTER_BUILD_NAME)</string>
	<key>CFBundleVersion</key>
	<string>$(FLUTTER_BUILD_NUMBER)</string>

[soury]

Yes of course, I'll leave it here as an attachment.
Info.plist.txt

[dam-ease]

Hmmn, if you try uploading to the store manually, the issue should reproduce. I did a Google search and found this thread with a solution that worked for this user - https://stackoverflow.com/a/76537098. Can you please try this out as well?

[soury]

🚀 How I Fixed the iOS Build & Publishing Issues on Codemagic

When publishing our Flutter app to App Store Connect via Codemagic, we ran into multiple errors:

• Invalid Bundle: Runner.app does not contain a bundle executable
• Missing CFBundleVersion / CFBundleShortVersionString
• Orientation / LaunchScreen validation errors
• Export compliance (“encryption”) missing

Here’s the solution that worked.

---

1. Override all required keys in Info.plist

We added a PlistBuddy script in codemagic.yaml to make sure all mandatory values exist and are correct.

Keys we enforced:

• CFBundleShortVersionString (marketing version, e.g. 1.0.0)
• CFBundleVersion (build number)
• CFBundleIdentifier (must match App Store Connect)
• CFBundleExecutable (Runner)
• CFBundleDisplayName (UI Park)
• CFBundleName (uipark)
• LSRequiresIPhoneOS (true)
• UIDeviceFamily (1 = iPhone, 2 = iPad)
• UISupportedInterfaceOrientations (Portrait, Landscape, etc.)
• UILaunchStoryboardName (LaunchScreen)
• CFBundlePackageType (APPL)
• ITSAppUsesNonExemptEncryption (false → avoids export compliance prompt)

👉 This fixed all validation errors from Apple.

---

2. Configure Code Signing

We forced Codemagic to use the right provisioning profiles with:

script: |
  xcode-project use-profiles --custom-export-options='{
    "method": "app-store",
    "testFlightInternalTestingOnly": true
  }'

👉 Ensures the IPA is signed for App Store distribution (TestFlight & App Store).

---

3. Separate Build & Packaging

Instead of relying on flutter build ipa, we split the process:

• Step A – Build iOS app without code signing:

  script: |
    flutter build ios --release --no-codesign \
      --build-name=1.0.0 \
      --build-number=$PROJECT_BUILD_NUMBER

• Step B – Package IPA with Xcode:

  script: |
    xcode-project build-ipa \
      --workspace ios/Runner.xcworkspace \
      --scheme Runner

👉 This guarantees that the binary (Runner) is created properly and packaged into a valid signed IPA.

---

✅ Result

• IPA successfully uploaded to App Store Connect
• Build processed correctly in TestFlight
• No more “Invalid Bundle” or “Conformity missing” issues

---

📌 Summary:
The fix was based on three pillars:

1. Full override of Info.plist (PlistBuddy script)
2. Explicit signing with use-profiles
3. Splitting build & IPA creation

This combination solved all App Store validation and publishing errors.