Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile

Developer Tools & Services Xcode
sergej_swiftlane OP
Created 1w
Replies 24
Boosts 7
Views 1.2k
Participants 15

We are seeing what looks like a signing / managed-capability mismatch for Contactless Pass Provisioning.

Environment

  • Team ID: S7AUTD2C2B
  • Bundle IDs:
    • com.swiftpass.ios
    • com.swiftpass.ios.dev
  • Xcode: 26.4
  • macOS: 26.4

Problem

Our app has had Contactless Pass Provisioning approved by Apple for a long time, and builds were working until a few days ago. Without any intentional signing/capability changes on our side, Xcode started failing with the following error:

Provisioning profile "Swiftpass prod Appstore" doesn't include the Contactless Pass Provisioning capability. Contactless Pass Provisioning capability needs to be assigned to your team and bundle identifier by Apple in order to be included in a profile.

Observed behavior

  • Xcode marks the relevant provisioning profiles as "Ineligible" in the profile selector.
  • This affects both development/debug and release/App Store builds.
  • If we remove Contactless Pass Provisioning from the app entitlements/capabilities, the exact same profiles immediately become eligible and the signing error disappears.

Important detail

The downloaded provisioning profiles already contain the entitlement that Xcode claims is missing.

We verified the downloaded profile with:

security cms -D -i /Users/sergej/Downloads/Swiftpass_prod_Appstore\(1\).mobileprovision

and it contains:

<key>com.apple.developer.contactless-payment-pass-provisioning</key>
<array>
<string>shareablecredential</string>
</array>

So the issue appears to be that

  • the profile contents look correct
  • the capability is still present in the developer portal
  • but Xcode's eligibility check still says the profile does not include the capability

What we verified

  • Contactless Pass Provisioning is still enabled for the App ID in the Apple Developer portal
  • Newly recreated / redownloaded profiles still contain the entitlement
  • Both dev and distribution profiles are affected
  • The behavior is reproducible across profile refreshes and local cleanup

What we already tried

  • Reinstalled Xcode
  • Updated Xcode and macOS
  • Updated command line tools
  • Cleaned DerivedData
  • Deleted local provisioning profile cache
  • Refreshed/redownloaded profiles from Xcode
  • Recreated provisioning profiles in the developer portal
  • Removed and re-added the capability in Xcode

Expected behavior If the downloaded provisioning profile contains com.apple.developer.contactless-payment-pass-provisioning, Xcode should treat that profile as eligible.

Actual behavior Xcode reports that the capability is missing and marks the profile as ineligible, even though the entitlement is present in the downloaded profile.

Question Has anyone seen this specific mismatch with Contactless Pass Provisioning or other managed capabilities? This currently looks like either:

  • an Apple backend/App ID capability-assignment sync problem, or
  • an Xcode eligibility-validation bug for managed capabilities

Feedback Assistant ID: FB22439399. It contains screenshots that showcase the issue as well.

Answered by DTS Engineer in 883734022

IMPORTANT There’s updated advice in this reply (i. 101537572, r. 174902737).

Wow, that escalated quickly.

When I replied earlier I thought that this was something specific to sergej_swiftlane’s situation. However, this is clearly affecting a wide range of folks. A colleague of mine uncovered a third-party developer bug about this (FB22439399) [1] and we’re escalating that internally.

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

[1] It may even be from one of you (-:

Replies  24
Boosts  7
Views  1.2k
Participants  15
Nagavendra OP
3d

Dear Team,

We request your urgent support to proceed with uploading our application to the Apple App Store. Currently, several of our customers are awaiting NFC credentials provisioning via Apple Wallet, and the delay due too thi issues and is directly impacting their onboarding and usage. This situation is significantly affecting our business operations and customer experience.

We kindly ask you to prioritize this request(102864920121.) and let us know if any additional information, changes, or compliance items are required from our side to expedite the process.

Your prompt assistance will be greatly appreciated, as many customers are actively waiting for access.

Thank you for your support.

1
DTS Engineer OP
Apple
2d
I’m talking with the right folks about this

I now have specific advice for folks in this situation:

  • Please re-apply for the Contactless Pass Provisioning capability.
  • The approval folks will then assign you the Contactless Pass Provisioning (deprecated) capability, which you can use right now.
  • Once this Xcode issue is resolved (FB22439399), they will assign you the newer Contactless Pass Provisioning (SharableCredential) to use going forward.

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

0
kpatel1991 OP
2d

Hi @DTS Engineer - we have re-applied for the capability however upon submitting the form we got a Server 500 error.

Could you advise what to do in this situation? Nothing seems to have changed in XCode either.

Thanks

0
ltanh OP
2d

Hi @DTS Engineer , When requesting Contactless Pass Provisioning for Enterprise Org, we can request the SharableCredential only. So it blocks us to build enterprise app locally. Do you have any ETA for the fix? Another question, on our AppStore Org, we already had Contactless Pass Provisioning (deprecated) capability. How long it will affect our AppStore app? Do I have to request the new SharableCredential for AppStore Org as well?

0
DTS Engineer OP
Apple
2d
we have re-applied for the capability however upon submitting the form we got a Server 500 error.

Well, that’s not good.

I reported this to the relevant folks, and they’re investigating.

My understanding is that this error is coming from the redirect that happens after the request was submitted, so your request actually did make it into the system.

When requesting Contactless Pass Provisioning for Enterprise Org, we can request the SharableCredential only.

My understanding is that you should use the current submission form, which requests the new capability, but you’ll been assigned the old capability until this issue is resolved.

Do you have any ETA for the fix?

No. I can’t talk about The Future™ [1].

on our AppStore Org, we already had Contactless Pass Provisioning (deprecated) capability.

Cool. That should keep you up’n’building until this issue is resolved.

How long it will affect our AppStore app?

I’m not sure I understand this. Are you saying that you’re having this problem when

  1. Signing for the App Store,
  2. And using only the Contactless Pass Provisioning (deprecated) capability?

Or have a misunderstood what you wrote? Regardless, please elaborate.

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

[1] For more on this, see tip 3 in Quinn’s Top Ten DevForums Tips.

0
kpatel1991 OP
1d

Hi @DTS Engineer - we do not see the "Deprecated" permission, the "ShareableCredential" one appears but even if we check it - XCode still isn't allowing us to deploy.

This is now materially impacting our business and we would appreciate rapid support.

0
Nagavendra OP
1d

@DTS Engineer : Thank you!

It’s working now with the following approach:

We contacted Apple Support and requested them to re‑enable Contactless Pass Provisioning(Deprecated). Apple enabled it for our account and generated a new provisioning profile. After using the new profile, everything is working as expected.

However, this does not seem like a proper or permanent solution. It is unclear who initially blocked this setting, but re‑enabling it from Apple’s side resolved the issue for us.

Hope this helps anyone facing a similar problem.

0
DTS Engineer OP
Apple
21h
the "ShareableCredential" one appears but even if we check it - Xcode still isn't allowing us to deploy.

Right. That is the nature of the bug in question here (FB22439399). You need to apply for the Contactless Pass Provisioning (deprecated) capability. There’s no form to do that specifically, so use the common Contactless Pass Provisioning capability form.

It’s working now with the following approach …

Excellent news.

However, this does not seem like a proper or permanent solution.

Indeed. The permanent solution will involve a fix to Xcode, which is what we’re tracking with the above-mentioned bug.

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

0
DTS Engineer OP
Apple
1h

Just now, I had already updated to the latest version Xcode 26.4.1, but the problem still persists.

Indeed. That’s expected. Xcode 26.4.1 does not contain a fix for FB22439399.

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

0
Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
First post date Last post date
 
 
Q