All geek questions in one place

How to send an application to the App Store using Xcode 4.3 or Application Loader

I have my first iOS app “Pending Download” in iTunes Connect, but I cannot send it to the App Store due to problems that I have in Xcode 4.3 in the Application Loader.

In Xcode 4.3, I have 3 provisioning profiles

  • Special training profile
  • Application repository provisioning profile (no valid signature identifier found) <- What does the signature mean? I downloaded it from the Provisioning portal!
  • IOS Team Training Profile

After creating and archiving my application, click "Distribute" and select "App Store for iOS". I enter the iTunes Connect username and password, but I get the following error message - There are no identifiers available for signing. What does it mean?

Error message - no identities available for signing

So, I tried using Application Loader. I selected Ad Hoc or Enterprise Distribution in Xcode and exported the application file to a folder. I selected this file in Application Loader, but received the following error: "Error checking application code." When did Xcode sign the application and with which profile?

It seems that most of the tutorials and documentation I found on the Internet are for older versions of Xcode. I have not changed some of my code signing and build settings without any luck.

Could you help me?

Thanx

+4
source share
6 answers

I am not sure about the certificates, but for my application I have this. In the initialization portal, go to "Certificates / Distribution" and make sure that you have a certificate and it is valid and you uploaded it - you must also have private keys! (don't forget the Apple WWDR certificate). Then, in Provisioning / Distribution, make sure you create a certificate for your application ID. It should work after configuration in Xcode (below).

But I know one thing. You do not need to submit your application through the Application Loader. When you open Xcode, go to your project. Create settings and configure distribution certificates. Then you need to archive the application - just change the startup scheme to the iOS device (in the upper left part of Xcode), then click on “Product” (in the Mac status bar) and “Archive”.

Once archiving is complete, open the Organizer tab and find the Archives tab. Then select your archive and click on "Check / Submit Application". It should be:)

NB: taken from the iOS Initialization Portal guide "Confirm that you select" Request a certificate from a certification authority ... "rather than" Request a certificate from a certification authority ... ", which means make make sure that the private key is not selected in keychain when creating a certificate.

+3
source

Somewhat obvious, but make sure your package id matches exactly. I tried all night to submit to the App Store and received the message "No Identity Available for Signing." It turned out that one letter was capitalized on the distribution profile and lowercase on the bundle identifier set in Xcode.

+2
source

This is actually a very common problem. If you want to download it, when exporting from Xcode, select "Save as Enterprise or Ad Hoc Deployment"

Choose this when exporting app

Do not send it to the ios app store. It should generate a .ipa file. Open the application loader, select the application that you want to add to iTunesConnect, and when it asks you about the file, select the .ipa file created by Xcode.

+1
source

It’s important to publish your application to verify that your Bundle ID matches the Bundle ID in iTunes Connect.

0
source

I had the same problem. To fix this, I went to the Provisioning Portal, then selected "Provisioning" on the left. Then I selected the Distribution tab and clicked the New Profile button to create a new application distribution provisioning profile.

0
source

I would have attacked Chris Lewd, but my representative is not tall enough. Chris - thanks, this led to a solution for me. In fact, I already had resource allocation profiles, but they just expired. The xCode error message just gave "No identifiers available for signing," although the private / public keys were correctly in the keystore. To fix this, I simply did the following:

  • In the Provisioning Portal iOS Portal, select Provisioning on the left.
  • In the "Provisioning Profiles" section, select "Distribution" (this is where I could see that provisioning profiles expired
  • Click on Expired Expired Profile
  • Click "Edit."
  • Select the certificate that you want to use for the Provisioning profile.
  • Click Create
  • Click Download
  • Open the file (it should launch xCode and add it to the Organizer)

After that, I was able to send the update to the App Store without problems. They really need a better error message.

0
source

Source: https://habr.com/ru/post/1401566/

More articles:


All Articles