exportArchive "Runner.app" requires a provisioning profile with the Associated Domains and Push Notifications features.

[shubham-settlin]

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

I have added these settings in codemagic.yaml file.

environment:
      ios_signing:
        distribution_type: app_store
        bundle_identifier: <my bundle id>
        
  scripts:
      - name: Set up code signing settings on Xcode project
        script: xcode-project use-profiles

The IPA is building correctly when I try building it locally, but it’s not working in Codemagic. Do I need to add the export-options-plist flag when building the IPA, or is this already handled by the "xcode-project use-profiles" command? In the log, I can see "Saved export options to /Users/builder/export_options.plist" with correct provisioning profile.

Also i have checked, all the capabilities needed are already added in provisioning profile. The certificates and provisioning profile are added in signing identities as suggested in the doc.

Expected results

IPA should be built and exported to app store connect.

Actual results

Building App Store IPA... (completed in 1,374ms)
[ ] Encountered error while creating the IPA:
[ ] error: exportArchive "Runner.app" requires a provisioning profile with the Associated Domains and Push Notifications features.

Build id (optional)

No response

[dam-ease]

Hello @shubham-settlin,
Yes, please add the --export-options-plist=/Users/builder/export_options.plist flag when building your IPA.
In general, this error could be caused by 2 main reasons:

1. With the Flutter build command, there is a flag that can be added to it --export-options-plist=/Users/builder/export_options.plist. When it is missing, you can see the same error.
2. You can check either in Xcode or the Apple Developer Account by finding the provisioning profiles to see if the required capabilities have already been enabled.

[shubham-settlin]

Thanks, it worked. However, I think this should also be included in the documentation, as there was no mention of specifically including the flag. I eventually figured it out, but I was targeting the wrong file location.