Xcode couldn't find any iOS App Store provisioning profiles matching [bundle ID]

Question

I always go with automatically manage signing when uploading builds to App Store Connect with Xcode and everything has worked great up until today.

After branching my project and adding push notifications when I try to upload a build I get these errors:

I've researched into this and looked at every single response on SO and elsewhere with no success. For testing purposes, I even created a new empty project with no additional code and when I try to upload it, this is what I get:

Things I've tried:

• Deleting both the Apple Distribution and Apple Development certificates and generate them again
• Clearing /Library/MobileDevice/Provisioning Profiles folder and manually downloading the profiles
• Deleting Derived Data
• Clearing the project
• Disabling 'automatically manage signing' and enabling it again

With manual signing I get to upload the build but I can't wrap my head around why the automatic option has stopped working. I've recently updated Xcode to version 13 and no other significant changes have occured.

What am I doing wrong?

Gosh

The same is happening to me, I didn’t find a solution yet – Usherette

were you using Xcode 13? – Inocenciainoculable

same here Xcode 13, moved project to another team where I have developer role and now Xcode couldn't find any iOS App Development provisioning profiles matching com.blablabla – Ascend

Answer 1

According to this: https://developer.apple.com/forums/thread/688626#689590022

You need to add the "Access to Cloud Managed Distribution Certificate" permission to your account in AppStore Connect.

Leo

Answer 2

If anyone comes across this you don't NEED to have Cloud Managed Distribution permission to upload to the App Store, this is only recommended for companies who don't want to pass around a .p12 distribution key to whoever is distributing the app.

In my experience, sometimes you have everything set up perfectly:

• Distribution cert/p12 key installed in your keychain
• App Store Distribution provisioning profile created associated with this cert

And Xcode still fails to find the profile during the Archive process, even with Automatic or by manually setting the profile in the Signing & Capabilities tab.

In this case, you can simply choose the Custom... option when you go to Archive your app and manually set the provisioning profile in the appropriate step.

Kimbra

You basically do not need ther permission. This actually works. – Kauri

Answer 3

Same issues with both my app where I have developer role. Everything signed well with my own apps. I found simple solution: just build it on previous Xcode 12.1 and published successfully. Seems that it is Xcode 13 "feature"..

Halfon