Template (custom entitlement) name not supported

App Store Distribution & Marketing App Store Connect API
mortion
mortion OP
Created Jul ’25
Replies 2
Boosts 1
Views 93
Participants 3

Hi All!

Ever since the new PLA I have issues with adding my entitlements to my profiles. Previously when adding an entitlement I used the format [entitlementName] [AppId] [type] e.g.

Apple Pay Pass Suppression [AppId] Development

However ever since the new PLA I get an warning in my terminal that the template name is not supported by the App Store Connect API.

Anyone that can help me out with the new format? I cant seem to find any helpful documentation online.

Thanks!

PS: the link in the screenshot points to this website: https://docs.fastlane.tools/actions/match/#managed-capabilities

The naming strategy the use on the website doesnt work either:

Apple Pay Pass Suppression Development
Answered by DTS Engineer in 856830022
Ever since the new PLA I have issues with adding my entitlements to my profiles.

I can’t help you with the fastlane side of this, but I can clarify what’s happening on the Apple side.

There are two ways that developers can gain access to managed entitlements:

  • The old school provisioning profile template mechanism
  • The newer managed capabilities mechanism

If you’re using the old mechanism, you’ll want to migrate to the new one. In this new world, you set the capability on your App ID and it automatically flows through to any appropriate provisioning profiles you create for that App ID. This has a bunch of benefits, not least of which is that it’s compatible with automatic code signing.

You seem to be a member of two different teams:

  • Your In-House (Enterprise) team has the Pass Presentation Suppression managed capability for Development, Ad Hoc, and In-House (Enterprise) signing. This is limited to two App IDs: TEAM_ID.n_.v_________l.v______k and TEAM_ID.n_.v_________l.h__d, where TEAM_ID is your Team ID and all the underscores are me redacting stuff for this public forum.
  • Your Organization team does not have the Pass Presentation Suppression managed capability.

So, if you’re trying to sign your app for your In-House (Enterprise) team then you can set the managed capability on your App ID, remote any attempt to use a template, and away you go.

OTOH, if you’re trying to sign your app for your Organization team then you’ll need to apply for the managed capability. If you were previously using a provisioning profile template, follow the advice in under Migrating additional entitlements to capabilities in Developer Account > Reference > Provisioning with capabilities. If this team has never been able to use this capability, you’ll have to apply for it via the standard path.

davelevi, It’s hard to help you here because it’s not clear whether you have an ongoing technical problem or not. If you do, the above explanation might help. If not, I’d be happy to dig deeper, but it’s probably best if we do this in a separate thread. Put it in Code Signing > Entitlements so that I see it go by.

Also, make sure to include the relevant Team ID because, unlike mortion, you’re a member of a lot of teams. If you’re not comfortable sharing that publicly, redact everything except the first and last letter. That should allow me to track it down.

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

Replies  2
Boosts  1
Views  93
Participants  3
davelevi
davelevi OP
6d

This is really messed up. I do work for a medical communications company, and their app uses critical alerts. Patient safety depends on this. This change that Apple made means that provisioning profiles were pretty much silently losing the entitlement that allowed critical alerts to work. This means recent builds in the app store may not be receiving critical alerts. Which means Apple has put patients' lives at risk with the boneheaded change. Seriously stupid on their part. I hope somebody for Apple is reading this ...

0
Apple Staff, DTS Engineer
DTS Engineer OP
Apple
5d
Recommended
Ever since the new PLA I have issues with adding my entitlements to my profiles.

I can’t help you with the fastlane side of this, but I can clarify what’s happening on the Apple side.

There are two ways that developers can gain access to managed entitlements:

  • The old school provisioning profile template mechanism
  • The newer managed capabilities mechanism

If you’re using the old mechanism, you’ll want to migrate to the new one. In this new world, you set the capability on your App ID and it automatically flows through to any appropriate provisioning profiles you create for that App ID. This has a bunch of benefits, not least of which is that it’s compatible with automatic code signing.

You seem to be a member of two different teams:

  • Your In-House (Enterprise) team has the Pass Presentation Suppression managed capability for Development, Ad Hoc, and In-House (Enterprise) signing. This is limited to two App IDs: TEAM_ID.n_.v_________l.v______k and TEAM_ID.n_.v_________l.h__d, where TEAM_ID is your Team ID and all the underscores are me redacting stuff for this public forum.
  • Your Organization team does not have the Pass Presentation Suppression managed capability.

So, if you’re trying to sign your app for your In-House (Enterprise) team then you can set the managed capability on your App ID, remote any attempt to use a template, and away you go.

OTOH, if you’re trying to sign your app for your Organization team then you’ll need to apply for the managed capability. If you were previously using a provisioning profile template, follow the advice in under Migrating additional entitlements to capabilities in Developer Account > Reference > Provisioning with capabilities. If this team has never been able to use this capability, you’ll have to apply for it via the standard path.

davelevi, It’s hard to help you here because it’s not clear whether you have an ongoing technical problem or not. If you do, the above explanation might help. If not, I’d be happy to dig deeper, but it’s probably best if we do this in a separate thread. Put it in Code Signing > Entitlements so that I see it go by.

Also, make sure to include the relevant Team ID because, unlike mortion, you’re a member of a lot of teams. If you’re not comfortable sharing that publicly, redact everything except the first and last letter. That should allow me to track it down.

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

0
Template (custom entitlement) name not supported
First post date Last post date
 
 
Q