Automatically manage signing with Apple Pay in project

Question

Created Jan ’21

Replies 2

Boosts 1

Views 5.2k

Participants 3

Hi.
I work in a bank and we added Apple Pay (adding card to wallet through it).
Everything works fine, but something wrong with signing.

I removed all provision profiles and created them on developer.apple.com with Entitlements containing “ApplePay In-App Provisioning Development”

File .entitlements contains <key>com.apple.developer.payment-pass-provisioning</key>
<true/>

And if I choose manual signing I can use these created profiles and everything is OK.

If I use "Automatically manage signing", I get an error
"Provisioning profile "" doesn't include the com.apple.developer.payment-pass-provisioning entitlement."

And it looks like Xcode recreate these profiles without Entitlements containing “ApplePay In-App Provisioning Development”, so it shows me this error.

What can I do to use “Automatically manage signing” with turn on apple pay?

Answered by Systems Engineer in 659620022

So this is one of those situations where it may be that you need to keep Manual Signing because this entitlement is a special entitlement that is granted on a per-developer basis. And the reason Xcode has an issue with Automatic Signing is because it is not able to verify that your Xcode managed profile can add this entitlement, like a traditional capability. However, to double check my logic, it would be good to review the XC managed profile, or the profile Xcode is referencing in Automatic Signing, on disk to see if there is a sync error between the profile on disk and the one in the Developer Portal. If the managed profile in the Developer Portal matches the one on disk, you just may have to keep Manual Signing enabled for this entitlement.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

Boost

Answer 1

Systems Engineer OP

Apple

Jan ’21

Accepted Answer

So this is one of those situations where it may be that you need to keep Manual Signing because this entitlement is a special entitlement that is granted on a per-developer basis. And the reason Xcode has an issue with Automatic Signing is because it is not able to verify that your Xcode managed profile can add this entitlement, like a traditional capability. However, to double check my logic, it would be good to review the XC managed profile, or the profile Xcode is referencing in Automatic Signing, on disk to see if there is a sync error between the profile on disk and the one in the Developer Portal. If the managed profile in the Developer Portal matches the one on disk, you just may have to keep Manual Signing enabled for this entitlement.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

2

Answer 2

marosoaie88 OP

Jan ’23

So this is one of those situations where it may be that you need to keep Manual Signing because this entitlement is a special entitlement that is granted on a per-developer basis. And the reason Xcode has an issue with Automatic Signing is because it is not able to verify that your Xcode managed profile can add this entitlement, like a traditional capability. However, to double check my logic, it would be good to review the XC managed profile, or the profile Xcode is referencing in Automatic Signing, on disk to see if there is a sync error between the profile on disk and the one in the Developer Portal. If the managed profile in the Developer Portal matches the one on disk, you just may have to keep Manual Signing enabled for this entitlement.

@meaton Is this still the case in Xcode 14? The docs mention that automatic signing is now possible with Apple Pay entitlements for merchants. Does that apply to banks too?

0