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

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

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 (-:

This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this.

AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test:

  1. Using the same Xcode, create a new project from the iOS > App template.
  2. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B).
  3. In Signing & Capabilities, make sure automatic code signing is enabled for all configurations.
  4. And that the correct team is selected.
  5. At the top, make sure that you have a test device selected as the run destination.
  6. Then add the Contactless Pass Provisioning (SharableCredential) capability.
  7. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish.
  8. Assuming that works, try running the app on a test device.

What do you see?

Share and Enjoy

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

Hi Quinn,

Thanks for such a quick response. I've done everything you suggested and at point 7 the error I stated in original post appears again.

I've run into the same issue as you. I also tried installing Xcode 26.3, and opening the project with the older version did work once. But for some reason the same problem reappeared later, and using 26.3 no longer helps.

I've run into the same issue as you. I also tried installing Xcode 26.4, Can you please share the any resolution ?

Since yesterday, I’ve been encountering the same issue as you. I hope the official team can resolve it soon. Thanks!

We've been getting this issue since yesterday too. Any updates? @DTS Engineer

Same here. We got this issue since yesterday. We faced the same issue as the author and tried everything they have done.

We have the same problem. This is happening as soon as we get the fresh code from Git and updates ur local environment. Other wise if we run the code on the local without any fresh pull nothing is affected.

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 (-:

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