No signing certificate "iOS Distribution" found

231.2k Views Asked by At

I am trying to sign an app with my client's certificates. I have received the following file from the client

enter image description here

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

enter image description here

How can I solve this issue? Any help is appreciated.

16

There are 16 best solutions below

3
Kassem Itani On BEST ANSWER

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) ?

Solution #1:

  • Revoke the signing certificate (reset) from apple developer portal
  • Create the signing certificate again on the same mac (keychain). Then you will have the private key for the signing certificate!

Solution #2:

  • Export the signing identities from the origin xCode
  • Import the signing on your xCode

Apple documentation: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html

3
Ragul On

Goto Xcode -> Prefrences and import the profile enter image description here

1
Greg Hilston On

Our solution was to run

fastlane match

as I forgot we setup a Matchfile.

1
Khalid Musa Sagar On

enter image description here

Solution Steps:

  1. Unchecked "Automatically manage signing".

  2. Select "Provisioning profile" in "Signing (Release)" section.

  3. No signing certificate error will be show.

  4. Then below the error has a "Manage Certificates" button. click the button.

enter image description here

  1. This window will come. Click the + sign and click "iOS Distribution". xcode will create the private key for your distribution certificate and error will be gone.
3
Naval Hasan On

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.

0
Rishav Kumar On

Double click and install the production certificate in your key chain. This might resolve the issue.

3
Hend El-Sahli On

Tried the above solutions with no luck ... restarting my mac solved the issue...

1
Phill Z On

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

  ...
0
Metin Atalay On

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/

0
user3305074 On

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.

0
Tyler A. On

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

0
Harrison Armitage-Bath On

The problem for us was the expiry of our Apple Developer Program membership

0
Eng.Ahmad On

Apple updated their agreement, so I had to

  • go to apple connect
  • accept the agreement
  • toggle automatic manage signing off and on
0
Dickson Phú On

Double click and install the production certificate in your key chain.

This might resolve the issue..

0
svdragster On

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

0
NPC On

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