Reputation: 1741
I am trying to sign an app with my client's certificates. I have received the following file from the client
I tried installing the ios_distribution
certificate and the key (.p12). Also I have installed the provisioning profile. Now when I try to sign the app with the provisioning profile, it does show up in the drop down but I get the following error:-
No "iOS Distribution" signing certificate matching team ID "7S977Lxxx" with a private key was found
How can I solve this issue? Any help is appreciated.
Upvotes: 115
Views: 262002
Reputation: 1
For me, turns out I was logged out of my account. You can reauthenticate by going to Xcode > Preferences > Accounts, sign out, and then sign back in.
Additionally, The message "No signing certificate 'iOS Distribution' found" indicates that Xcode cannot find a valid iOS Distribution certificate for your app. Solution:
Upvotes: 0
Reputation: 20386
This happened to me after I changed my mot de passe.
I had to reauthenticate in the Mac Systems Settings as well as in XCode.
For lick on Xcode -> Settings... -> Accounts -> sign in again
Upvotes: 2
Reputation: 4110
In my case, i just had to agree to the latest Program License Agreement from app store connect
Upvotes: 6
Reputation: 81
It sounds like you were logged out or a failure with the signing cert process happened on the OSX. In my case - a restart solved it. You can uncheck the Automatic manage signing, and check it again (after restart) and it will work
Upvotes: 1
Reputation: 341
I had to reauthenticate in the Mac Systems Settings as well as in XCode.
For XCode 15, click on Xcode -> Settings... -> Accounts -> sign in again
Upvotes: 9
Reputation: 101
Apple updated their agreement, so I had to
Upvotes: 7
Reputation: 51
The problem for us was the expiry of our Apple Developer Program membership
Upvotes: 2
Reputation: 3068
I literally just went to "Signing & Capabilities" for my build target and took no further action and the next build worked.
Merely visiting that screen seemed to update the Signing Certificate
Upvotes: 4
Reputation: 834
If you are sure to have the cert. included in your provisioning profile but still getting this issue then give below steps one try.
Turn off you mac's internet access.
Tick Automatic manage signing.
Untick automatic manage signing.
Turn on you mac's internet access.
Error should go away.
Explaination for steps:
Sometimes xcode couldn't sync settings automatically. Above steps update it manually.
Upvotes: 0
Reputation: 1517
I am working for an enterprise company so we archive the app on more than mac. The issue is related to computers count. You should archive the app a mac which was created certified on keychain.
Identifier and Profiles are the same but don't forget that you create a certificate for each mac machine.
So, We need to have as many certificates as there are computers. The below link is useful for creating a certificate.
https://blog.codemagic.io/how-to-code-sign-publish-ios-apps/
Upvotes: 0
Reputation: 6732
Tried the above solutions with no luck ... restarting my mac solved the issue...
Upvotes: 26
Reputation: 141
I got the "No signing certificate" error when running Xcode 11.3 on macOS 10.14.x Mojave. (but after Xcode 12 was released.)
I was also using Fastlane. My fix was to set generate_apple_certs
to false
when running Match. This seemed to generate signing certificates that were backwards-compatible with Xcode 11.3
Match documentation - https://docs.fastlane.tools/actions/match/
This is the relevant section of my Fastfile:
platform :ios do
lane :certs do
force = false
match(type: "development", generate_apple_certs: false, force: force, app_identifier: "your.app.identifier.dev")
match(type: "adhoc", generate_apple_certs: false, force: force, app_identifier: "your.app.identifier.beta")
match(type: "appstore", generate_apple_certs: false, force: force, app_identifier: "your.app.identifier")
end
...
Upvotes: 1
Reputation: 5450
Double click and install the production certificate in your key chain. This might resolve the issue.
Upvotes: 0
Reputation: 1147
You need to have the private key of the signing certificate in the keychain along with the public key. Have you created the certificate using the same Mac (keychain) ?
Apple documentation: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html
Upvotes: 39
Reputation: 1510
I had the same issue and I have gone through all these solutions given, but none of them worked for me. But then I realised my stupid mistake. I forgot to change Code signing identity to iOS Distribution from iOS Developer, under build settings tab. Please make sure you have selected 'iOS Distribution' there.
Upvotes: 83
Reputation: 406
Solution Steps:
Unchecked "Automatically manage signing".
Select "Provisioning profile" in "Signing (Release)" section.
No signing certificate error will be show.
Then below the error has a "Manage Certificates" button. click the button.
Upvotes: 30
Reputation: 2424
Our solution was to run
fastlane match
as I forgot we setup a Matchfile.
Upvotes: -5