App Store Connect API ProfileCreateRequest is missing template property

Hi,

In the web portal of developer.apple.com when you create or edit a provisioning profile there is a possibility to set "Entitlements", which is I understand also called as "Template". Our project has such entitlements, like NSE Filtering or CarPlay.

But in the ProfileCreateRequest https://developer.apple.com/documentation/appstoreconnectapi/profilecreaterequest there is no possibility to provide such parameter, this is why we are not able to automate our flow of provisioning profile update.

Is there any workaround? Or maybe I need to fill a request to improve this API?

Answered by DTS Engineer in 876840022

I’m not an expert on the App Store Connect API, but I can speak to this part of your question:

there is a possibility to set "Entitlements", which is I understand also called as "Template".

The entitlement template feature is very much an old school path. These days most access to managed entitlements is via additional capabilities. Like any other capability, you set these on your App ID and they flow through to every provisioning profile [1] you create for that App ID.

These capabilities have a bunch of advantages, including Xcode integration, compatibility with automatic signing, and the ability to add any combination of the capabilities to a given profile. Given that, the template mechanism is largely deprecated.

If you have existing templates you can request that they be migrated to additional capabilities. See Developer Account Help > Reference > Provisioning with capabilities > Migrating additional entitlements to capabilities. That’s the path I recommend you pursue here.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Assume the profile type and platform are aligned. See Finding a Capability’s Distribution Restrictions.

I’m not an expert on the App Store Connect API, but I can speak to this part of your question:

there is a possibility to set "Entitlements", which is I understand also called as "Template".

The entitlement template feature is very much an old school path. These days most access to managed entitlements is via additional capabilities. Like any other capability, you set these on your App ID and they flow through to every provisioning profile [1] you create for that App ID.

These capabilities have a bunch of advantages, including Xcode integration, compatibility with automatic signing, and the ability to add any combination of the capabilities to a given profile. Given that, the template mechanism is largely deprecated.

If you have existing templates you can request that they be migrated to additional capabilities. See Developer Account Help > Reference > Provisioning with capabilities > Migrating additional entitlements to capabilities. That’s the path I recommend you pursue here.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Assume the profile type and platform are aligned. See Finding a Capability’s Distribution Restrictions.

App Store Connect API ProfileCreateRequest is missing template property
 
 
Q