xcode 4.2, code signing for distribution

Question

I have finished coding my app and have spent the last 2-3 days on figuring out why and what I am doing wrong with building an archive to be uploaded to apple app store.

1 - I verified that my new app is in "Waiting for Upload" state.

2 - I have download and double click on the WWDR intermediate certificate. Verified that this exist in my key chains.

3 - I verified that my distribution certificate is not expired. It's expiration date is a year from today. Its status is "Issued"

4 - I have created app id. I verified that the app name space portion is exactly the same as my application name space. The states that this app is in are: - push notification: configurable (yellow) - in app purchase: enable (green) (i want to turn this off, but there's no way to) - game center: enable (green) (i want to turn this off, but there's now way to) - iCloud: configurable (yellow)

5 - I have verified that my distribution provision is "Active" for the correct application id.

6 - i have downloaded and installed and installed all 3 where they belong: a - WWDR intermediate certificate b - Distribution certificate c - Distribution provisioning profile

I have Xcode 4.2 with IOS 5. I did an update on the app store for the latest version of XCODE 2 days ago.

In Xcode -> organizer - Devices: under "Developer Profile" i have verified that I have the correct provision profile for distribution under "Provisioning Profiles" i have verified that I have the correct provision profile for distribution

in Xcode -> project -> build setting: i have verified that I specified the correct code signing provision under "Code signing Identity" for both debug and release type. debug: i point to my developer provision release: i point to my distribution provision

in Xcode -> target -> build setting i did the same as the project describe above.

I left "Code signing entitlements" blank I left "code signing resource rules path" blank i left "other code signing flags" blank

I modify the schema for "iOS device" for "archive", i specified: "release" under "build configuration" "nameOfMyApp" under "archive name" i have checked "reveal archive in organizer"

I made sure that my project is compile for all static library.

I then click on "Product" -> "Archive"

The project compiled, there was no compilation error. (i verified that my app ran on my iPhone)

Toward the end of the archiving a window for codesign pop up. the message says in exact letters: "codesign wants to sign using key "" in your keychain." I allow it. (is "" suppose to have some other name other than "key"?)

After I click allow, I see "build succeeded"

I go to the organizer -> Archives, I do not see any item under this section. the organizer shows "No Archives" for the left pane. and the main panel.

I go to the path where the archive would be shown, I see the archived file, but the size is "Zero byte"

So I search this forum for help, and someone posted a link to a guide: https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933

I went over this link in very good detail, but still NO luck.

I've been on this issue for a very long time and it's driving me mad and crazy. There are no error returned, thus I have no idea how to fix this issue.

Would someone help me out?

Also is there a phone number that apple provide to support issue like this? If there is, please provide it here.

After 3 months of development, my app is done and just sitting on my computer and not on the app store. sigh......

Yes, in XCode logs, you should see the name of the key which was used to sign. When you open Keychain on your Mac, does it show that you have private key in your certificate? — Aditya Kumar Pandey
thanks for your preliminary answer. I have private and public key for developer certificate and the distribution certificate. — Daniel Nguyen
I up ticked you for the effort you put into explaining your situation. I'm in the same situation. I've been working on this app for 14 months and thought I would submit today but now I suddenly have code sign errors AND new memory issues. Blech! — kpierce8
Why don't you try uploading the binary through application loader? — DonDyck
did you press "always allow"?, i think there's a bug with 'always allow' button and you need to click just 'allow' — Steve Ham

USS1994 USS1994 · Accepted Answer · 2012-01-01T21:55:03

The method you described deviates a little from the method that I just recently used. Try following this guide:

http://www.touch-code-magazine.com/how-to-upload-an-app-to-the-app-store-with-xcode-4/

It worked perfectly for me and seems to be a different method than what you did. It uses the xcode interface directly to go all the way through the upload process. (aka, you don't need to manually upload the file via your internet browser)

EDIT:

Also try: http://www.weston-fl.com/blog/?p=2442

xcode 4.2, code signing for distribution

3 Answers