Bugfix: Ignore uncompatible devices when creating provisioning profiles #200
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.
There is a bug in
app-store-connect fetch-signing-files
action related to provisioning profile creation. When requested AdHoc or development provisioning profile, that is profiles that can contain allowed devices identifiers, does not exist then the tool automatically tries to include all eligible devices registered in Apple Developer Portal in the new profile during creation.However, up until now Apple TV devices were also included when iOS provisioning profiles were created, which is not allowed, despite the fact that devices Apple TV devices share the same platform attribute with iPhones, iPads, iPods and Apple Watches.
This makes the Create a Profile request
fail with
409
error response:Now distinct separation is made using the
deviceClass
attribute on the device resource to filter out which devices can be included in the provisioning profile.Updated actions:
app-store-connect fetch-signing-files
.