Improvement: xcode-project use-profiles
logs for set code signing settings
#203
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.
Sometimes building Xcode projects with
xcode-project build-ipa
fail with errors such aseven though before running the build, action
xcode-project use-profiles
was called, and the code signing settings were seemingly successfully configured.Usually the reason for this is that
xcode-project use-profiles
did not assign usable provisioning profile to the Xcode targetTargetName
, which is actually required for successful Xcode project build.The aim of this PR is to make it clearer when such conflicting code signing settings happen. This is achieved by two steps.
First make it possible to further debug what settings were configured for each found Xcode project target by logging
code_signign_manager.rb
output always to debug log file. Also make it possible to include this output toxcode-project use-profiles
output via new command line switch--code-signing-setup-verbose-logging
without the need to enable fully verbose log output.Second and perhaps more notable change for end users is that
xcode-project use-profiles
now shows warnings about targets for which code signing settings were not updated. The warning are based on targets for which code signing settings were set to avoid excess noise.Updated logs
Updated actions:
xcode-project use-profiles
.