Adding support for custom profile template name input #18
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.
Checklist
step.yml
andREADME.md
is updated with the changes (if needed)Version
Requires a MINOR version update
Context
(Copied from bitrise-io/go-xcode#191)
For a subset of Entitlements a special approval is needed from Apple to enable a new option to select custom Provisioning Profile templates in Developer Portal. The known ones are listed here.
We added a check earlier to fail automatic provisioning if one of these entitlements was in use.
Apparently this prevents one of the customers to manually edit the provisioning profiles to circumvent the limitations of the Apple API.
So we no longer fail, only print a warning.
In addition there seems to be an undocumented API that we can use to specify Profile Template Name as implemented by Fastlane. Added this feature as experimental, as more testing and feedback is needed.
The template name can be extracted from the Apple Developer Portal: bitrise-steplib/steps-ios-auto-provision-appstoreconnect#31 (comment)
(end)
Resolves: https://bitrise.atlassian.net/browse/SWAT-817
Changes
Investigation details
Decisions