ChatGPT解决这个技术问题 Extra ChatGPT

Provisioning profile doesn't include signing certificate (Xcode 9.3)

After upgrading to macOS 10.13.4 and Xcode 9.3, my project now makes all my Provisioning Profile ineligible! They worked before upgrade.

The error message for the distribution profile is:

Provisioning profile "distribution profile name" doesn't include signing certificate "development certificate name"

So I search through the forum,

remove ALL items in keychain My Certificate

redownload the distribution profile (double tap to install to Xcode)

create new distribution profile (double tap to install to Xcode)

recreate the Production certificate (double tap to install to Keychain)

redownload the Development certificate (double tap to install to Keychain)

So now my keychain has two production certificate (one is newly created), and one development certificate, and the error is still there. I found it weird that it asked for the development certificate in distribution profile? (I think this is a clue but I don't know why and what to do.)

So now what should I do? Please help!

Do you have the private key for your certificates? When you view your certificates in the keychain, do you have the ability to expand them to see a private key underneath (should be a little triangle that lets you see the private key. If not, you will need to fully recreate your certificates from a new private key.

f
franiis

I got two options for you:

1) open KeyChain and find the signing certificate that shown in the error message then delete it.

2) you specified the signing certificate in the Build Setting->Signing, so go to the Build Setting->Signing and click the Code Signing Identity. Do not select Automatic (iOS Developer or iOS Distribution), select the one of the signing certificates in the Identities in Keychain which is valid and have associated with the Provisioning Profile.


Deleting the extra certificate worked! Kudos to you for saving me from exceeding the go-live date on my app!
Kudos !!!!! this totally worked, I think the long-term solution is to have a much better-defined fast file , but he gives me more time to get to it. Thank you so much !! [[ What I mean by a long-term solution: dev.to/matt_catalfamo/…
tried both, not working
L
Lim Thye Chean

I temporary solved the issue by going into Build Settings, and manually set Code Signing Identity (the old way). "Automatically manage signing" no longer work properly, but at least it work.


D
Dinesh Nagarajan

For XCode 11 and later make sure to update the profile certificate updated with "For use in Xcode 11 or later" which resolves the issue for me.

https://i.stack.imgur.com/Aog3B.png


where can i found this setting ?
In developer account with the certificate mapped with the project.
This! On developer.apple.com go to Profiles, select your Profile and Edit. Your certificate appears twice, one has "Xcode 11 and later" behind. I selected both but that one is probably enough. Re-download and import again. There is a large extra space reserved in hell for Apple's development eco-system
This was the only thing that fixed the issue for me. I had exported my developer account from the old mac laptop - but that didn't do it. I had to regenerate my profile with all Developer Certificates selected.
@dube Thank you so much! Now i can finally stop using the automatic signing
A
Andreas Braun

"Automatically manage signing" is not working on Xcode 9.3. Code signing identify should be selected manually in Build Settings.

It is right. You can select Code Signing Identity as iOS developer for development and iOS distribution for production in Signing of build settings.


I did not even know it was possible for the signing settings to skew in this way, but mine were and your answer pointed me to it. Thanks!
The key for me was to go into the Build settings, where I could change what certificate to use manually. (Xcode 13.2)
A
Abhishek

check out screenshot it says it all...

Targets>>Build settings>>(search)Product bundle identifier>>this was wrong for me :(

https://i.stack.imgur.com/iVnCU.png


T
Taras Gleb

You need to make sure that:

Your Apple Development -> Certificates, Identities & Profiles all have the correct provisioning profile "distribution profile name" that include signing certificate as in fig 1. below Same inside xCode

https://i.stack.imgur.com/qbvsx.png


A
Andreas Braun

"Automatically manage signing" is not working on Xcode 9.3. Code signing identify should be selected manually in Build Settings.


s
stevex

In my case, the Provisioning Profile on developer.apple.com listed two developer certificates. One was selected, and one was not. Changed it so both were selected, saved that, installed the updated profile and that fixed it.


This one helped in my case when I was using fastlane match and it created two certificates instead of single one.
R
Ruuhkis

I had to juggle a bit more too. I deleted my keychain, enabled and disabled autosigning before recreating my certificates.

Then I toggled the certificates in Build Settings section and finally I was able to select the correct certificates in general section.

Really missing the simplicity of signing for Android.. :P


K
Kexi He

In my case, I changed the Provisioning Profile to solve the problem by changing the Certificate whose type is "iOS Distribution" to another Certificate whose type is "(Distribution) For use in Xcode 11 or later", then download it and import it to keyChain, select it form Xcode.


Yeah, was able to fix it, by clicking on the provisioning profile, editing it, and adding iOS Distribution to the list of certificates.
S
Sara Inés Calderón

In my case I had multiple profiles and various certs. I had to go to Apple developer and edit the profile from the error, and add every cert to it, and then it worked.


D
DanSkeel

If you have this certificate on another machine, you can export it from keychain and import on the other.

My problem was that I didn't know how to match private keys with certificates because I used "all items" filter in KeyChain.

If you switch to Certificates private keys are arranged under certificates, so you can easily export the right pair.


This didn't work for me. Even though I had exported all my certificates from the Keychain on my old device, and they showed as correct in the Keychain on the new machine. Xcode wasn't recognizing everything it should be. The answer provided by Dinesh (to regenerate Profile from developer.apple.com) worked.