Code sign error the identity iphone developer

Code Sign error: Certificate identity ‘iPhone Developer: My Name (xxx)’ appears more than once in the keychain

I m stuck with this error:

Code Sign error: Certificate identity ‘iPhone Developer: My Name (xxx)’ appears more than once in the keychain. The codesign tool requires there only be one.

I try to renew the build a new CSR, remove the old certificate, build a new one, again and again and again and this error is still present

in the keychain I dont see any duplicated certificate and if I remove the only one I can see in the keychain , Xcode complains that the certificate can’t be found .

14 Answers 14

Xcode 4.3 now searches all keychains for signing certificates but that is increasing the frequency of the build error:

Certificate identity (x) appears more than once in the keychain.

However, if you are affected by the keychain bug mentioned in the final note of that guide, following is a simpler and preferred solution to problem:

1) Keychain Access > Edit > Keychain List, uncheck «Shared» for the login keychain.

2) next, IF going back into the Keychain List you find the login keychain is still marked as Shared, create a backup of the following files and then remove them if they exist:

3) Retry your build.

I’ve had the same issue after updating XCode to 4.3. Deleting certificates and provisioning profiles didn’t change anything. There were no duplicates or expired ones anyway.

It turned out the problem was that my private key was in both the session and the system keychains in the keychain access. I just had to remove it from the system keychain and i could build my projects again.

I’ve had the same issue and I fixed it deleting every certificate from my keychain, every provisioning from my Xcode and every provisioning profile from my device and later. redone it again. I guess, It normally happens when you are working with differents profiles and you have created many certificates for the same provisioning.

I’ve had the same issue as well. I think you can get to this state in a variety of ways, but for me, it was because a certificate had recently expired.
What I didn’t realize was that Keychain Access will hide expired certificates. Go under «View» and make sure you’re not hiding the duplicate certificate.

If you already deleted all other Developer Certificates in your KeyChain and the Error is still coming up, then try to delete all old/unused keys (private key) with your name. The one that’s necessary, is the one with the little «folder-enhancer-icon» next to its name. Keeping this and deleting the rest fixed it for me.

I had the same problem. I checked every related question I could find on SO and followed the steps — but had no luck. It kept telling me that my distribution cert appeared more than once, but I could see that it only appeared once. I revoked certificates and closed X-Code many times, but it turned out that there was a ‘hidden’ certificate. I had an older Distribution Certificate that was not in the login keychain. It was in an unnamed keychain. When I deleted that one, it worked! So its worth looking around keychain access thoroughly!

After moving to a new development mac, I had this problem. I tried deleting the duplicates and checking that there were no hidden expired ones, but the error persisted. The solution that worked for me was to copy the keychain pair from the old mac and imported it in the new mac. The problem was then solved with the following:

• select the certificate in Keychain Access
• Expand the arrow to see the private key
• Double click the private key
• Click Access Control
• Choose ‘Allow all applications to use this item’
• Click Save Changes

For me, I was then able to rebuild the app successfully.

Hope that helps someone 🙂

This works sometimes for me:

• Delete all duplicates that you can see from the keychain (normally this step on itself does not help me)
• Then also delete (or at least temporarily rename/move

/Library/Developer/Xcode folder. Xcode keeps old crap/cache in there. I guess profiles exist there. Waste em. (Note that the path of this folder is changeable in Xcode prefs so if you changed the path, go there and delete stuff instead.)

Then rebuild. Worked for me this minute after getting this error the millionth time.

Try to remove certificates from the xcode organizer.

Источник

Xcode Code Sign error because of no Keys in Keychain

You might think, not again such a question where are already thousands of topics about. However, I’ve not been capable of finding the answer I needed to fix this problem.

None of these topics go as deep as the Keychain.

When I’m trying to deploy my app to an iPhone, I’m receiving the following message:

Now, as said, I have been looking for multiple guides or fixes, however, none of them seemed to fix this issue.

Things I’ve tried:

• Use Apple’s walkthrough for app deployment for countless of times
• Searched the internet for guides for app deployment
• Changed the content of the ‘pbxproj’ file inside the ‘xcodeproj’ package.
• Retrieve all available profiles from Apple’s server using the Refresh button in Xcode 4.6 (allows you to obtain automatically)

After trying all of these ways, I’ve still not been able to solve the issue. One problem I’ve seen is that at first hand, the certificate in the Keychain was showing an invalid status, which is now solved.

However, if I’m right, there are supposed to be two keys attached to the certificate. A public and private key, and these are not showing.

Neither are there any keys showing in the Keys tab in the Keychain Access.

Solution

(Thanks to nsgulliver)

1. Do everything what the post (marked as Solution) of nsgulliver says.
2. If you already have an active Certificate, click the Revoke button, this won’t cause any trouble, you’ll simply have to re-create the keys of which then will be generated a new certificate.
3. Make sure you have the WWDR of Apple installed to mark the certificate authority as valid.
4. Follow the default Provisioning Assistant guidelines.

Источник

Code Sign error: The identity ‘iPhone Developer’ doesn’t match any valid certificate/private key pair in the default keychain

How do you fix this XCode error :

Code Sign error: The identity ‘iPhone Developer’ doesn’t match any valid certificate/private key pair in the default keychain

12 Answers 12

This happens if you forgot to change your build settings to Simulator . Unless you want to build to a device, in which case you should see the other answers.

I ‘tripped’ across my solution after 2 days. XCODE 4.0

I’ve just upgraded to XCode 4.0 and this code signing issue has been a stunning frustrastion. And I’ve been doing this for over a year various versions. so if you are having problems, you are not alone.

I have recertified, reprovisioned, drag and dropped, manually edit the project file, deleted PROVISIIONING paths, stopped/started XCODE, stopped started keychain, checked spelling, checked bundle ID’s, check my birth certificate, the phase of the moon, and taught my dog morse code. none of it worked.

1. Goto Targets. Build Settings tab
2. Go to the Code Signing identity block
   • Check Debug AND Distribution have the same code signing information ..in my case «IPhone Distribution:, dont let DEBUG be blank or not filled in.

If the Debug mode was not the same, it failed the Distribution mode as well. go figure. Hope that helps someone.

Figure: This shows how to find the relevant settings in XCode 4.5.

Check if you are building for device instead of simulator. Go to Xcode menu ‘Project’ -> ‘Set Active SDK’ change from ‘Device’ to ‘Simulator’

Under Xcode 4.1 Check your build settings for the project and your targets. For each check under ‘Code Signing’ check ‘Code Signing Identity’ and change over to ‘Don’t Code Sign’

I had the same problem. I’m very new to iphone development and it was my first time trying to load my program onto my iphone. The message is correct, you need to create a certificate in the keychain. The best walkthrough is here:

You of course need to have a developer account (need to have paid the $100 yearly fee).

I hope this helps.

I had the same problem. I was very new to iPhone development and it was my first time trying to submit my app to App-store.

Check the following :

1. Check that your current «Bundle Identifier» is same as your current «Provisioning Profile» name in «Code Signing Identity».

2. In «Code Signing identity block» — Check Debug AND Distribution have the same «Code Signing Information». Try to keep the «Code Signing Information» same in all the Blocks.

3. Try to Download the «Provisioning Profile» again and double click on the profile. Then use that newly downloaded profile in your «Code Signing Identity».

4. Try to Download the «Certificate» again from the «developer.apple.com» and double click on the certificate. (It worked in my case)

Then «Clean» the project and click on «Build for Archive». Hope your code will be archived perfectly.

This usually happens to me when I forget to change the company to match mine.

1. Select the target under Groups & Files
2. Click the Get Info button
3. Choose the Properties tab
4. Under Identifier, make sure it says com.YOURREALCOMPANYNAME.APPNAME

When you create a new app, it usually says, «com.yourcompany». Change it to whatever you registered with, in my case com.DavidKanarek

In XCode 4.0 main workspace, at the top left side & just after the «Stop Button», there is scheme selector, click on it and change your scheme to IPhone Simulator. That’s it

When I had this problem, the issue was I did not have the private key necessary for the developer certificate to be valid.

The solution was:

Have the developer who created the certificate export their private key matching the iOS developer public key. see http://developer.apple.com/ios/manage/certificates/team/howto.action

Open this file (Certificates.p12) on your machine (with KeyChain), and enter the password the other developer used when exporting. It is now imported into your KeyChain.

Now connect iOS device and rebuild targeting the iOS device.

In my case, I didnt have the Apple Root certificate. It can be found here:

if your certificate is not valid, it will have a red «x» and state the reason why. Generally the reason is «This certificate has expired» or «This certificate was signed by an unknown authority.

to solve this you need to do the following step.

1. If your certificate has expired, renew it at the iPhone Portal, download it, and double-click it to add it to your Keychain.
2. If it’s «signed by an unknown authority», download the «Apple Worldwide Developer Relations» certificate from the Certificates section of the iPhone Developer portal and double-click it to add it to your Keychain.
3. If your certificate was revoked, delete the certificate from your Keychain, then follow the «Obtaining your iPhone Development Certificate» or «Obtaining your iPhone Distribution Certificate» section in the iPhone Developer Program Portal User Guide to generate a new certificate.
4. Make sure you create a backup of your private key. The steps for doing this are described in the iPhone Developer Program Portal User Guide, under «Saving your Private Key and Transferring to other Systems».
5. If you have the iPhone Developer (or iPhone Distribution) certificate and its associated private key, the Apple WWDR Intermediate certificate is installed, and your certificate is valid, confirm that Online Certificate Status Protocol (OCSP) and Certificate Revocation List (CRL) are set to «Off» in Keychain Access > Preferences > Certificates.
6. if you still getting problem then contact support apple community.

Источник

iOS Code Signing Troubleshooting

Retired Document

Important: This document may not represent best practices for current development. Links to downloads and other resources may no longer be valid.

iOS Code Signing Troubleshooting

Important: This document may not represent best practices for current development. Links to downloads and other resources may no longer be valid.

This document aids in troubleshooting problems relating to iOS code signing, or issues encountered while performing any of the common tasks involving code signing. This guide is intended to supplement the Tools Workflow Guide for iOS , so start there first if you are new to iOS development.

Code Signing in a nutshell

Code Signing is the process by which your compiled iOS application is sealed and identified as yours. The following sections describe the two major players in code signing: signing certificates and Provisioning Profiles.

Signing Certificates

Signing certificates (also referred to as Code Signing Certificates) are issued to each team member of the iOS developer program and they must be properly installed to perform the following development related tasks. The certificate named «iPhone Developer» allows you to run/debug your app on iOS devices through Xcode, and the certificate named «iPhone Distribution» allows testing your submission build with Ad Hoc distribution, submitting your app to the App Store, or creating an Enterprise build for in-house distribution.

Steps within this guide show how to create the iOS certificates, verify they are correctly installed, or transfer them to another machine if you choose to. A Certificate and its Private Key together can be referred to as ‘identity’ or ‘Code Signing Identity’.

Note: Only team admin and agent roles have access to create or manage the iPhone Distribution certificate on the iOS Portal site.

Provisioning Profiles

Provisioning Profiles work with your signing certificates to enable certain tasks for your app. For example, depending on which profile you choose when code signing your app, it determines whether your app can be run and debugged on your device thru Xcode, submitted to the app store for distribution, or sent to testers through Ad Hoc distribution. Different profiles are needed in each case, and you are responsible for creating them and configuring your Xcode project to use the right ones in each situation. The steps in this guide show you how and when to use provisioning profiles, and to verify they are correctly installed.

Note: Once you have a healthy working code signing configuration set up it is recommended that you follow the steps in section Transferring Your Identities to create a backup of them. This backup can be used to restore your working code signing configuration from hardware failure, or to enable code signing on additional Macs, partitions, or OS X user accounts of your choice.

Common Tasks Involving Code Signing

A healthy working code signing configuration is required to perform the following iOS development related tasks:

The recommended procedures for these common tasks are below, but before engaging these tasks use the following sections to verify your Xcode Project and Keychain satisfy the requirements for code signing.

Requirements for Code Signing

Add your iOS Device to your Team Devices List

Before you can debug/run your application on your development device through Xcode, your development device must be added to your Team Devices List on the iOS Provisioning Portal. The following steps describe leveraging Xcode to do this for you.

A) If you are a team «Agent» or «Admin» within your developer program, follow these steps: choose the Xcode «Window» menu > Organizer, and click the Devices tab. Right-click the target device under the «DEVICES» section of the left-sidebar, and choose «Add Device to Provisioning Portal». If prompted, enter your developer program credentials into the popup, and click OK.

B) If you are not a team «Agent» or «Admin», follow these steps: choose the Xcode «Window» menu > Organizer, and click the Devices tab. Select the target device under the «DEVICES» section of the left-sidebar. Select and copy to the clipboard the 40-digit hexadecimal «Identifier» string and send that to your team agent or admins and ask that they add it to the «Devices» section of the provisioning portal.

Once your device has beed added to the provisioning portal, perform the steps in section Provisioning Profile Refresh to allow Xcode to update, download and install your Team Provisioning Profile that includes the newly added Development Device.

Create your signing certificates

Use Xcode’s Provisioning Profile Refresh feature to automatically create your signing certificates on your behalf. Every iOS Developer Program team member gets an iPhone Developer certificate. Only the team Agent gets an iPhone Distribution certificate.

Provisioning Profile Refresh

Xcode’s Provisioning Profile Refresh feature (also referred to as Automatic Device Provisioning) automates setting you up to run apps on iOS devices thru Xcode in basic development situations. It is useful to know the individual tasks being performed by this feature in the event you wish to utilize those tasks individually. The tasks are:

To invoke Provisioning Profile Refresh, open Xcode’s «Window» menu > Organizer > Devices tab > «Provisioning Profile» sidebar under Library and click the Refresh button. The first time refresh is pressed, a prompt appears requesting your team member credentials. It is important to answer positively when asked to create your signing certificates if they are needed. To do that, click «Submit Request» when you are prompted and Xcode will create, download and install the certificate(s).

Additionally, if an iOS development device is connected to your machine while the Refresh button is clicked, Xcode will install the updated iOS Team Provisioning Profile onto your device. The result of invoking Provisioning Profile Refresh should be a quick setup to enable running your app on device through Xcode in basic development situations. To learn more about «non-basic» development situations, see the section titled Cases Where Custom Provisioning Profiles are Required .

Note: In the case of missing Private Keys for your certificates, Provisioning Profile Refresh can restore your certificate to the keychain, but not the missing private keys. Therefore, see the section titled Transferring Your Identities to restore your Private Keys from backup, or from the mac in which they were created. Alternatively you can follow the steps in section How do I delete/revoke my certificates and start over fresh? to generate new certificates. Use the section titled Verify Your Private Keys to clarify whether or not your private keys are present.

Provisioning Profile Refresh Troubleshooting: If you are receiving the error message:

Create your Provisioning Profiles

Provisioning Profiles are used during the Xcode build process to sign your application. There are different types of provisioning profiles and depending on which one you pick to sign your app it determines where that particular build can be used. Code Signing with a development profile allows your app to run on device through Xcode, and signing with a distribution profile allows you to create distribution builds.

There are different types of distribution profiles and depending on which type you pick to code sign your app it determines whether the app can be submitted to the App Store, installed on company devices, or installed on beta test devices.

In most cases, you are required to create and install these different types of provisioning profiles into Xcode yourself. The previous section explains the case where Xcode creates and installs a basic provisioning profile on your behalf. That profile is called the iOS Team Provisioning Profile and it can be used to run your app on device through Xcode in most development cases. In contrast, now continue to the section Cases Where Custom Provisioning Profiles are Required .

Cases Where Custom Provisioning Profiles are Required

Following describes the situations where custom provisioning profiles must be created by you manually.

Before you can create a distribution build for submission or installation on company or beta test devices, you must create a distribution provisioning profile on the «Distribution» tab of the iOS Portal site > Provisioning section. Access to the «Distribution» tab is available only to Admin and Agent team members.

Sharing profiles across apps saves you the administration time of creating and maintaining profiles for each app, and that is one of the main benefits of using an Implicit Wildcard App ID. The following bulleted items will help you determine which of your apps can share the same profiles.

Apps that require special Application Entitlements (Code Signing Entitlements) require Explicit App IDs.

All applications requiring special entitlements are those which utilize any of the following features: Push Notification, Game Center, In-App Purchase, or iCloud. Custom profiles are required in this situation because they are used to transfer the custom entitlements onto the app’s signature during the code signing process.

You are only required to create custom Development Provisioning Profiles for explicit app IDs.

Custom development profiles are created on the provisioning profile on the «Development» tab of the iOS Portal site > Provisioning section.

Although an explicit app ID is not strictly required for all projects, having one, and the related provisioning profiles, gives you finer control over who can build and run each app you create. This is done by choosing which team members are included in the custom development provisioning profile you create for your app.

Applications that do not utilize any of the specialized development features listed above are allowed to reuse the same iOS Team Provisioning Profile to run your apps on device through Xcode, and those apps may also reuse the same Distribution Provisioning Profile as long as it is associated to an Implicit Wildcard App ID.

After you create, download and install your custom Provisioning Profiles into Xcode by dragging them onto either the Xcode or iTunes icon on your Dock, you must follow the steps in section Assigning Provisioning Profiles to Build Configurations to instruct Xcode to use them during the build process.

Keep Your Profile Library Clean

Xcode automatically imports signing certificates into your Keychain based on the provisioning profiles in your library. You need to manually remove provisioning profiles you are not using, otherwise, Xcode will reimport potentially old or duplicate certificates into the keychain and that can cause build errors.

To clean your profile library, go to the Xcode Window menu > Organizer > Devices tab > Provisioning Profiles section under the Library sidebar. In the center pane, ctrl-click and delete all profiles with status «expired» or «Valid signing identity not found». Profiles with either of these statuses are useless, as they cannot be used to code sign an application, and will likely cause ‘duplicate certificate’ build errors.

Transferring Your Identities

Once you have a healthy working code signing configuration set up it is recommended that you follow the steps in section Safeguarding and Transferring Your Signing and Provisioning Assets of the Tools Workflow Guide for iOS to create a backup of them. The backup can be used to restore your working code signing configuration from hardware failure, or to enable code signing on additional Macs, partitions, or OS X user accounts of your choice. The backup (.developerprofile file) once created contains all of the following items:

Note: While creating the backup of your identities you will be asked to enter a brand new password. Be sure to remember as you’ll be asked to enter that password later to use the backup for its intended purposes.

Verify Keychain configuration

Use this section to verify your signing certificates and their associated Private Keys are properly installed.

Verify Your Signing Certificates

In Keychain Access, choose «Certificates» in the Category sidebar, then type «iPhone» into the upper-right search field. Select your iPhone Developer or iPhone Distribution certificate and check the header pane for a green check mark and text reading «This certificate is valid» to ensure the certificate is properly installed.

To create your signing certificates, see the section Provisioning Profile Refresh .

Verify Your Private Keys

In Keychain Access, choose «Certificates» in the Category sidebar, then type «iPhone» into the upper-right search field. Check for Grey Disclosure Triangles to the left of your signing certificates to confirm your Private Keys are present. Xcode cannot code sign your app with your certificate if the private key is missing. To correct the latter situation, you can either import your private key from a backup if you have it using the steps in section Transferring Your Identities , or follow the steps in section How do I delete/revoke my certificates and start over fresh? to generate new ones.

Figure 2 Verifying your signing certificates in the login Keychain, Certificates category.

Note: If instead your certificate shows a Red Circle with White ‘X’ and status «This certificate was signed by an unknown authority», simply download and install the «Apple Worldwide Developer Relations Certification Authority» certificate from the iOS Portal > Certificates section and link reading «WWDR intermediate certificate», then double-click the downloaded file to install it into the Keychain.

Note: If instead your certificate shows a Blue Circle and White Plus sign, there are Trust problems with your certificate that should be resolved per the steps in section How do I resolve the CodeSign error: CSSMERR_TP_NOT_TRUSTED? .

Verify Xcode Project configuration

This section verifies your Xcode project settings are correct.

Verify Base SDK

It is recommended that the «Base SDK» setting on your Xcode Project is set to «Latest iOS». The following steps define the Base SDK at the Project level:

1) Choose the Xcode «View» menu > Navigators > Project, and then select your root project folder in the upper left corner, and the Project Editor will appear in the center pane.

2) Click on your project in the «PROJECT» section, then click the «Build Settings» tab.

3) Under the «Architectures» section, set the Base SDK setting to «Latest iOS».

The following steps define the Base SDK at the Target level:

1) Choose the Xcode «View» menu > Navigators > Project, and then select your root project folder in the upper left corner, and the Project Editor will appear in the center pane.

2) Click on your target in the «TARGETS» section, then click the «Build Settings» tab.

3) Under the «Architectures» section, set the Base SDK setting to «Latest iOS».

Note: If you are building to your development device, the Base SDK version number defined on your Xcode project must be greater than or equal to the software version number on your development device; otherwise Xcode cannot initiate a debugging session with the device. In that case, you will need to download and install the latest iOS SDK version that is greater than or equal to your device software version.

Verify the iOS Deployment Target

The «iOS Deployment Target» Xcode setting defines the iOS software version your application is built for; it specifies the lowest version of iOS Devices your application will support. For example, the lowest available setting for iPad applications is iOS 3.2.

To verify this setting, choose the Xcode «View» menu > Navigators > Project, and then select your root project folder in the upper left corner. The Project Editor will appear in the center pane. Make sure Deployment Target is set to the intended value in both locations: pick your project under the «PROJECT» section, then click the «Info» tab > iOS Deployment Target. Also click your target under the «TARGETS» section, then click the «Summary» tab > Deployment Target setting.

Figure 4 Setting the iOS Deployment Target at the Project level. Figure 5 Setting the iOS Deployment Target at the Target level.

For more information, see Specifying the Targeted iOS Version in the Tools Workflow Guide for iOS.

Verify the Target Architectures

You must verify that the target architectures are defined in your build settings according to architectures of the iOS devices you intend your app to support.

If for example, your deployment target is set to iOS 4.2 or lower, then armv6 must be included in addition to armv7. For more information, see the document QA1760 — iPhone/iPod Touch: application executable is missing a required architecture.

Additionally, see Specifying the Targeted Architecture within the Tools Workflow Guide for iOS for more information.

Verify the Device Type Setting

To ensure your app runs on all the iOS devices you intend your application to support, you must verify the Device Family setting on the Target > Summary tab.

If for example, the Device Type is set to «iPad» the app will not install on iPhone or iPod Touch. For more information, see Specifying the Device Type within the Tools Workflow Guide for iOS.

Verify Building for a Device (not Simulator)

For debugging your application on device, or creating a distribution build, make sure «iOS Device» is chosen in the Scheme pop-up selection menu in the upper-left corner of the Xcode toolbar. When a device is connected, it will show that device’s name instead of «iOS Device».

Figure 6 Selecting the active Run Destination.

For more information, see Specifying the Runtime Environment > Specifying the Run Destination, within the Tools Workflow Guide for iOS.

Defining a Bundle Identifier in Xcode that is compatible with your App ID

The Bundle Identifier setting on your app’s Xcode Project must be compatible with the App ID associated with your Provisioning Profile. To define the Bundle Identifier in your Xcode project, choose the Xcode «View» menu > Navigators > «Project» option, then select your root project folder in the upper left corner. The Project Editor will appear in the center pane. Select your target in the «TARGETS» section, then click the «Info» tab. Enter your bundle identifier in the «Bundle identifier» field. If a wildcard asterisk character is present in your App ID, replace the asterisk with an appropriate string using reverse-DNS format for the Bundle Identifier defined on your Xcode project.

Here are some example App IDs and compatible corresponding Bundle Identifier values defined in Xcode:

If your App ID is A1B2C3D4E5.com.domainname.applicationname enter com.domainname.applicationname as your Bundle Identifier.

If your App ID is A1B2C3D4E5.com.domainname.* enter com.domainname.ichosethisappname as your Bundle Identifier.

If your App ID is A1B2C3D4E5.* enter any string you like using reverse-DNS format as your Bundle Identifier.

Figure 7 Defining the Bundle Identifier in the Target ‘Info’ tab.

To ensure the Xcode project Bundle Identifier is compatible with the App ID associated with your Provisioning Profiles, perform the following steps. Choose the Xcode «View» menu > Navigators > Project, and then select your root project folder in the upper left corner. The Project Editor will appear in the center pane. Click on your target in the «TARGETS» section, then click the «Build Settings» tab. Scroll down to the «Code Signing Identity» section. If you are building to your development device, click the Value column under «Debug» that is to the right of «Any iOS SDK». In the provisioning profile selection pop-up, check that the current selection reads «For Application Identifiers: » with the intended App ID. If you are building a distribution binary, click the value column under «Release» that is to the right of «Any iOS SDK». In the provisioning profile selection pop-up, check that the current selection reads «For Application Identifiers: » with the intended App ID.

Assigning Provisioning Profiles to Build Configurations

For new projects, Xcode defaults all Code Signing Identities to the ‘Developer’ Automatic Profile Selector. This allows simple-case projects to be debugged/ran on the development device without change to your Xcode Project configuration. However, you must manually assign Provisioning Profiles to Build Configurations to create builds for App Store or Ad Hoc distribution, and for all other situations covered in section Cases Where Custom Provisioning Profiles are Required . Here are the steps to assign Provisioning Profiles to Build Configurations in Xcode:

1) Choose the Xcode «View» menu > Navigators > Project, and then select your root project folder in the upper left corner.

2) The Project Editor will appear in the center pane. Click on your target in the «TARGETS» section.

3) Click the «Build Settings» tab.

4) Make sure that both of the following buttons are depressed on the button row immediately below the Build Settings tab: «All» and «Combined».

5) Scroll down to the Code Signing section. Click on the Grey Disclosure Triangle to the left of the «Code Signing Identity» setting to expand and make visible the settings for «Debug», «Release», and «Any iOS SDK».

If you are building to your development device, verify that the Code Signing Identity setting for «Debug» has a child setting named «Any iOS SDK». Set the value of the Any iOS SDK line to «iPhone Developer» under the «Automatic Profile Selector» menu section. Using the Automatic Profile Selector setting allows Xcode to select the right profile for you, which makes your Xcode project easier to share amongst team members.

If instead you are building a distribution binary, verify that the Code Signing Identity setting for «Release» has a child setting named «Any iOS SDK». Set the Value column (that is to the right of the text «Any iOS SDK», under «Release») to the correct «iPhone Distribution» provisioning profile. In most cases, it is recommended that you pick the value «iPhone Distribution» under the «Automatic Profile Selector» section of the pop-up selection menu as this allows Xcode to pick the correct provisioning profile for you. However, in situations where there are two Distribution Provisioning Profiles that are compatible with the Bundle ID defined in your Xcode Project (e.g. an Ad Hoc, and App Store) then you will need to select the Provisioning Profile yourself from the list. Note that you are required to create, download and install Distribution Provisioning Profiles yourself; see the section Steps to submit your app to the App Store for more details.

Figure 8 Setting the ‘Debug’ Code Signing Identity using the ‘Automatic Profile Selector’ option. This allows Xcode to choose the right provisioning profile for you. The numbers in this figure correspond to the steps above. Figure 9 Example Code Signing Identity Settings. The ‘Debug’ Code Signing Identity is set to a Development Provisioning Profile, and the ‘Release’ Code Signing Identity is set to a Distribution Provisioning Profile. Also note, only the setting for ‘Any iOS SDK’ is assigned a Provisioning Profile, and every other line is set to the value ‘Don’t Code Sign.’

Perform Common Tasks

Once your Xcode Project and Keychain satisfy the requirements for code signing defined in the previous sections, continue to perform any of the following:

Steps to run your app on device thru Xcode

1) Connect your device to your development machine and verify that the device is listed under the DEVICES section on the sidebar of the iTunes Application. If your device is not recognized by iTunes, ensure you have a working USB data cable and that the connectors are fastened securely to the device and development machine.

2) If you haven’t already done so, indicate to Xcode that your device may be used for development: choose the Xcode «Window» menu > Organizer, and click the Devices tab. Select the device from the left-pane. In the center pane, click the button «Use for Development». This must be done again after upgrading the iOS version on your device.

3) Ensure that the iOS Deployment Target defined on your Xcode Project is less than or equal to the iOS software version installed on your Development Device. To check the software version installed on your device, open the Xcode Window menu > Organizer, click the Devices tab, and select your device from the left-pane. The software version will be shown in the center pane. Follow the steps in section Verify the iOS Deployment Target to define your iOS Deployment Target setting in Xcode.

4) Ensure your target device is added to your Devices list on the Provisioning Portal by referring to section Add your iOS Device to your Team Devices List .

5) Ensure that the Base SDK version number defined on your Xcode project is greater than or equal to the software version number on your development device. If it is not, Xcode cannot initiate a debugging session with the device. In that case, you need to download and install the latest iOS SDK version that is greater than or equal to your device software version. See the section Verify Base SDK for information on checking this setting.

6) Verify that your Run Task is set to the Debug Build Configuration. To check this, follow the steps in section Creating an Application Archive to bring up the «edit scheme» popup. However, verify the Build Configuration for the Run Task is Debug.

7) Follow the steps in section Assigning Provisioning Profiles to Build Configurations to verify your iPhone Developer identity (under Automatic Profile Selector) is assigned to your Debug Code Signing Identity.

8) Depending on the iOS version installed on your device Xcode may require that you download an option debugging support package within the Xcode «Preferences» menu > Downloads tab > Components.

9) Invoke the Xcode Product menu > Run.

Steps to Test Your Submission Build with Ad Hoc distribution

Ad Hoc distribution gives you the ability to enable the app to run on your beta testers’ devices who use only iTunes to install the app. Ad Hoc distribution is a very important step in the development process as it is the only way to fully test the actual submission build before submitting the app to the App Store.

Note: Running your app on device through Xcode does not replace Ad Hoc testing because Xcode does not fully test all possible exhibitions of the app. For example, Watchdog timers are suppressed while connected to Xcode’s debugger so Ad Hoc testing is the only way to ensure your app is free of issues like Watchdog crashes .

Therefore, to test your submission build on tester devices before it is submitted to the App Store, follow these steps:

1) Confirm that a distribution signing certificate exists in your keychain with its associated private key using section Verify Your Signing Certificates . To create your distribution signing certificate, see Provisioning Profile Refresh .

2) Add tester’s iOS devices to your team using the steps linked here . Then Create a distribution provisioning profile with Distribution Method set to Ad Hoc, if you have not done so already. After making changes such as adding new testers to your team, use Provisioning Profile Refresh to instruct Xcode to download the updated profile.

3) Assign the Ad Hoc profile to your Release code signing identity similar to the steps described in section Assigning Provisioning Profiles to Build Configurations .

4) Build and create the installable «.ipa» file according to the steps in section Creating an Application Archive

Note: While creating updated versions of your Ad Hoc builds during the Testing process, remember to increase your application’s «bundle version» Info.plist property for each build. Doing so allows iTunes to recognize the update and properly sync the new .ipa to the test device.

For more information on creating and distributing Ad Hoc builds for Testing, see the iOS Development Workflow Guide section Publishing Application for Testing .

Steps to submit your app to the App Store

Follow these steps to submit your app to the app store:

1) Ensure that your build is free of issues that can only be tested in Release builds (such as Watchdog crashes , etc) by using the Steps to Test Your Submission Build with Ad Hoc distribution .

2) Confirm that a distribution signing certificate exists in your keychain with its associated private key using section Verify Your Signing Certificates . To create your distribution signing certificate, see Provisioning Profile Refresh .

3) Create a distribution provisioning profile with Distribution Method set to App Store, if you have not done so already. To confirm it is properly installed, see How do I confirm my Provisioning Profile is for App Store distribution? .

4) Assign your app store profile to your Release code signing identity as pictured in section Assigning Provisioning Profiles to Build Configurations .

5) Build and submit your app according to the steps in section Creating an Application Archive

Creating an Application Archive

The advantage of the Application Archive is it allows you to sign and distribute the same build to the App Store that passed your Ad Hoc tests. It also files away the .dSYM file that is unique to the submitted build so it can be used later for crash log symbolication.

1) before creating an application archive, verify the Scheme «Archive» Task is using your release build configuration, as pictured in the following figures:

Figure 10 Click the Scheme menu in the upper left corner of the Xcode Toolbar. Figure 11 Choose ‘edit scheme..’ Figure 12 In the Edit Scheme popup, click the ‘Archive’ task in the sidebar, and verify the Build Configuration in the center pane is ‘Release’.

2) build the Application Archive by invoking the Xcode Product menu > Archive. The archives organizer opens up as seen in #1 in the figure below.

Figure 13 The Archives Organizer Distribute Flow Figure 14 Choose the appropriate distribution method

3) Choose the «Submit …» option to submit your app to the store.

Important: For the submission to work you are required to select your App Store Provisioning Profile in the «Code Signing Identity» field during the submission flow.

Note: If your application is not available in the «Application» field, see the «Ready to Upload Your Binary» section of the iTunes Connect Developer Guide for steps to prepare iTunes Connect for your binary.

4) Choose the «Enterprise or Ad Hoc» option to create an enterprise build, or a beta application for testers. For the build to install correctly you must supply your Enterprise or Ad Hoc provisioning profile within the «Code Signing Identity» field during this flow. Save the resulting «.ipa» file to disk and share it with your users. The .ipa is installed by dragging it into the Library sidebar in iTunes.

Steps to create an Enterprise build for In-House distribution

The process of creating an enterprise distribution build is similar to the Steps to Test Your Submission Build with Ad Hoc distribution , with the exception that the «Distribution Method» chosen while creating your Enterprise Distribution Provisioning Profile on the iOS Portal website will be «In House» instead of «Ad Hoc». And, unlike the Ad Hoc process, enterprise distribution does not require target devices to be pre-registered on the iOS Portal prior to creating the enterprise distribution provisioning profile.

For more information on Enterprise Distribution, see the Distributing Enterprise Apps for iOS Devices guide.

Troubleshooting FAQ

This section answers common code signing questions as they apply to all iOS Developer Programs, and is categorized as follows:

Источник