No signing certificate "iOS Distribution" found

user_3034944 0
Viewed 167918

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.

mobileprovision ipa provisioning-profile ios-provisioning ios
11 Answers

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.

user_78557240

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

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

user_95224060

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

  ...
user_108180000

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

user_2348360

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

user_98100400

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/

user_34506150

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.

user_33050740

Our solution was to run

fastlane match

as I forgot we setup a Matchfile.

user_19839570
Related