Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

No Identities are available for signing in Xcode 5

I have followed every direction given here but in-vain.

Created/Added distribution provisioning profile (1000 times) Deleted and created certificates. Added them to keychain. Create distribution profile using new certificate.

I get no warning or error when i build the app. It is only when i am trying to archive the app to create ad-hoc distribution i get No Identities are available for signing warning. If I try use download Identities, Xcode crashes.

This started to happen ever since I upgraded to Xcode 5.

Certificate as well as profile have Valid status. Also I made sure to pick correct distribution provisioning profile under code signing identity for both target and project.

Here is one of the links i followed.

https://stackoverflow.com/questions/13592074/no-identities-are-available-for-signing

like image 499
Kurt Watts Avatar asked Oct 05 '13 21:10

Kurt Watts


People also ask

How do I enable signing in Xcode?

Open the project using Xcode. Select the root project directory, and go to the Signing and Capabilities tab. Here, you can either check Automatically manage signing or do the signing manually. If you check the Automatically manage signing checkbox, then you will just need to select the Team from the drop-down list.

Where is Code Signing Identity in Xcode?

In Xcode an integrated development environment (IDE), it appears as an option in the build setting as a list option from which developers can select the Identity to be used for CodeSign.

What is code signing in Xcode?

Code signing your app assures users that it's from a known source and hasn't been modified since it was last signed. Before your app can integrate app services, be installed on a device, or be submitted to the App Store, it must be signed with a certificate issued by Apple.


2 Answers

Xcode 5

1) Recreate the distribution profile in developer.apple.com with a different name.

download / open

cmd + , - > preferences > accounts > view details > sync /refresh

3) under the Build Settings

Provisioning profile > Release > Select the new Provisioning profile.

Above - in code signing identity and it should magically appear.

like image 166
johndpope Avatar answered Oct 13 '22 04:10

johndpope


Ran into this issue today also when trying to create Ad Hoc builds for upload to TestFlightApp. Fixed it by updating the Target - Code Signing Provisioning Profile section. Set the Release Provisioning Profile to point to your Ad Hoc profile. Then when you create a package from the Archive menu item it will use the correct profile for Ad Hoc distribution. This looks to be new in XCode 5.

enter image description here

like image 44
mservidio Avatar answered Oct 13 '22 05:10

mservidio