Skip to main content

explicit provisioningProfiles mapping doesn't override Xcode project settings

Updated today

Issue:

The error message you may get:

❌  error: No profile for team '****' matching 'match Development com.'****' found: Xcode couldn't find any provisioning profiles matching ''****/match Development com.'****'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor. (in target ''****' from project ''****')
❌  error: No profile for team '****' matching 'match Development com.*****.imagenotification' found: Xcode couldn't find any provisioning profiles matching '****/match Development com.*****.imagenotification'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor. (in target 'ImageNotification' from project '*****')

This is likely occurring because explicitly setting export_method in build_app (legacy: gym) or match doesn't override what is set in the xcode project settings. This can lead to an error where codesigning fails to get the appropriate provisioning profile, or the wrong distribution method is used, even though it seems to be set correctly in Bitrise and in their chosen fastlane lane.

Possible solutions:

One possible solution is to use our Update Xcode Project Provisioning Step:

If that does not successfully resolve the issue, we would recommend looking at this GitHub issue thread.

Did this answer your question?