Provisioning profiles can be created using action app-store-connect create-profile, or as a side-effect when running app-store-connect fetch-signing-files with --create option. There were couple of issues linked to the devices that are included in the created profile.
All development and ad-hoc profiles require devices and cannot be created without any device relationships. Otherwise App Store Connect API returns an error response. Hence there is a validation in API client method which raises a ValueError in case devices are missing but requried. This error was not handled on caller side however, and hence actions that created profiles failed unexpectedly.
Action app-store-connect create-profile had --device-ids as a required argument, which is not correct as release profiles are not expected to contain any devices and as such user should not specify any device IDs when creating such provisioning porfiles.
Due to the changes in this PR:
Release profiles can now be created without specifying any device IDs
Actions fail with explanatory error message in case devices are required for profile creation, but are not specified
$ app-store-connect create-profile SQBQYNTA52 --certificate-ids 2YLULF4YA4 --type IOS_APP_DEVELOPMENT
Get Bundle ID SQBQYNTA52
Creating new Profile: name: 'io codemagic banaan kana ios_app_development 1701343403', profile type: IOS_APP_DEVELOPMENT, bundle id: SQBQYNTA52, certificates: ['2YLULF4YA4']
Cannot create profile: the request does not include any iOS testing devices while they are required for creating a IOS_APP_DEVELOPMENT profile. If the profile creation is automatic, ensure that at least one suitable testing device is registered on the Apple Developer Portal.
Provisioning profiles can be created using action
app-store-connect create-profile
, or as a side-effect when runningapp-store-connect fetch-signing-files
with--create
option. There were couple of issues linked to the devices that are included in the created profile.ValueError
in case devices are missing but requried. This error was not handled on caller side however, and hence actions that created profiles failed unexpectedly.app-store-connect create-profile
had--device-ids
as a required argument, which is not correct as release profiles are not expected to contain any devices and as such user should not specify any device IDs when creating such provisioning porfiles.Due to the changes in this PR:
Release profiles can now be created without specifying any device IDs
Actions fail with explanatory error message in case devices are required for profile creation, but are not specified
Updated actions:
app-store-connect create-profile
app-store-connect fetch-signing-files