Fix setting provisioning profile specifiers for specific SDKs #371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting code signing settings for Xcode project with
xcode-project use-profiles
does not override platform-specific provisioning profile assignations. For example, if my project file already contains entry such asthen running
xcode-project use-profile
just adds anotherPROVISIONING_PROFILE_SPECIFIER
definition for the target:which results in a conflicting provisioning code signing setup because both profiles are defined in the
project.pbxproj
file:Now, if the original profile that is referenced for specific SDK does not exist in
~/Library/MobileDevice/Provisioning Profiles
, which might very well be the case when build is running on a VM from CI environment, thenxcodebuild build
is destined to fail.Changes to
code_signing_manager.rb
ensure that allPROVISIONING_PROFILE_SPECIFIER
build settings for target are properly updated whenxcode-project use-profiles
is launched.Updated actions:
xcode-project use-profiles