Quantcast
Channel: Active questions tagged react-native+ios - Stack Overflow
Viewing all articles
Browse latest Browse all 16552

Why does provisioning profile need to be set to distribution for both debug and release?

$
0
0

I'm attempting to build my react native app via fastlane on CircleCI. I'm using match for managing certificates/profiles and using these guides:

fastlane ios beta works locally.

On CI however, I found the setup failed to build, with the following error:

error: No profile for team '...' matching 'match Development app.my' found: Xcode couldn't find any provisioning profiles matching '.../match Development app.my'. 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 'MyApp' from project 'MyApp')`

I thought this was strange, because I'm not using the development profile for my build, but instead the distribution profile. This is confirmed in the build output when match/gym are invoked, where there is no mention of the development profile.

In Xcode, under "Signing & Capabilities", I had "automatically manage signing"unticked as per the above guides, with "debug" set to use the development provisioning profile, with "release" set to use the distribution profile.

Changing the provisioning profile to "release" under the "debug" section was what fixed my CI builds, but why is this? Surely my debug builds should always use a development certificate?


Viewing all articles
Browse latest Browse all 16552

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>