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

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.

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

We're having the same issue in our project. Any way we can track this feedback ticket? Or progress on when this is fixed?

We're experiencing the same issue and wanted to add our voice to this thread. Our app also has the Contactless Pass Provisioning capability approved and has been working fine for a long time, but we started seeing the exact same "Ineligible" profile error a couple of days ago — without any changes on our end. We've confirmed that the entitlement (com.apple.developer.contactless-payment-pass-provisioning) is present in the downloaded provisioning profile, and the capability is still enabled in the Developer Portal. Despite that, Xcode continues to mark our profiles as ineligible. This is now blocking us from releasing an important bug fix to our customers. We'd really appreciate any update on the timeline for a resolution. Is there anything we can do in the meantime to work around this, or should we simply wait for a fix on Apple's side? Thank you for escalating this internally.

We are also experiencing the same issue, please can we get an update ASAP.

@DTS Engineer Hello, is there any new progress now? Because of this issue, we are unable to release the app on the App Store. Thank you!

We are also experiencing the same issue in 3 devices using xcode 26.3

is there any new progress now?

No. I’m talking with the right folks about this, but I don’t yet have a path forward that I can recommend.

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

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.

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"

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

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?

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.

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.

@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.

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"

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"

Is that the only conclusion? Are there no subsequent solutions available?