iOS 7.0 No code signing identities found

Question

• certificate is valid
• xcode 5
• iOS 7

Code Sign error: No codesigning identities found: No codesigning identities (i.e.

Answer 1

I had this ambiguous error, "Command /usr/bin/codesign failed with exit code 1", when I was setting up new Jenkins boxes for iOS builds with Xcode 7.3, OSX 10.11.4.

In my case I had several things right: 1.Yes I had added my certificates to the keychain, both Apple's root and the team's cert. 2.Yes I downloaded the correct provisioning profile via xcode preferences. 3.Yes it even built manually in xcode.

However, for jenkins, there was perhaps a caching issue on xcode. What worked was: 1.Exit the Xcode GUI. 2.Get back in, and run the build manually once. 3.Only then will Xcode prompt to allow keychain access authorization. 4.Jenkins has some settings that might be able to fix this, but my machines are secure, so I click 'always allow xcode to access the keychain'.

Answer 2

For Certificate

1. Revoke Previous Certificate.
2. Generate New Development Certificate.
3. Download Certificate.
4. Double Click to put in KeyChain.

For Provisioning profile

1. Create New or Edit existing Provisioning profile.
2. Download and install.

For BundleIdentifier.

1. com.yourcompanyName.Something (Put same as in AppId)

CodeSigningIdentity.

1. Select The Provisioning profile which you created.

Answer 3

it might sound strange but for me worked restarting my mac..i cant explain why and what happened but it works now. hope it will helps someone

Answer 4

I reached this thread when I am using pure command line/jenkins build script and I don't want any single UI/RDP manually setup for the integration environment.

After a few hours try to solve exactly the same issue using jenkins.
The key is "security list-keychains -s <your_keychain_name>"

--- Long story ---
I use a script in jenkins to override per-project settings (provisioning profile and signing identities)
After upgrade to Xcode 7, I have to change the script add above "list-keychains" after "create-keychains"

Updated script here.

Answer 5

you need not to delete all your profiles.I had same issue and fixed it by installing the missing certificates. You might forgot to install the required certificate for the provisioning profile you are using for code signing.

• make sure that you installed desired certificates(development/distribution) into keychain for the code-signing provision profile(development/distribution).

Answer 6

Make sure that your certificate is connected with your private key:

Open Keychain access, login, Certificates. Find the certificate inside the list and see if it is properly paired with your private key.

If certificate is not signed with private key, delete it, go to apple developer page and create new certificate. Sometimes it will be needed to revoke old. This new certificate will be now properly signed with your private key.

Now, when you have new certificate, recreate needed provisioning profiles that will include new certificate in creation process.

Note, when somebody from your team reset this certificate with his private key, this same problem can appear again during the refresh process. I am not sure, but it seems that every developer in team must have own certificate for distribution.