1 person found this helpful
Welcome to the wonderful world of Apple signing.
Is there any way you could do all the code signing on the Mac? It's
going to be challenging to decipher what the problem is using the method
you outlined below.
The only thing I can suggest is to make absolutely sure that you're
using Distribution provisioning profiles along with the matching
Distribution cert. I've created a number of tutorials showing the
process for creating Distribution profile/certs here:
It could be in the way the cert is created with openssl, hard to tell
"Welcome to the wonderful world of Apple signing" never seen anything like it - it's a wonder that any Aps end up in the AppStore.
I'll go through your tutorials today and start afresh from my mac but in the mean time could you / someone clarify a few points for me:
- When I create the Signing request: how critical are the email address and Common name. E.g. do they have to be identical to those I used to configure my account (or something else...) in developer.apple.com?
- The P12 file - is that specific to AIR signing or does the normal XCode packager (or whatever that's called...) use an identical mechanism
- I am utterly confused about this WWDR intermediate file. At which stage should I import it into my key chain: before, after which step
I thought writing good Aps was the tricky bit!
3 Days later - I figured it out and for the rest of the world who will ever try to do the same thing:
- I use CS5.5 to develop my Apps which comes with AIR 2.6
- Air 2.6 runs like a (slow) dog on iPhones so I installed AIR 3.1 and I created a seperate XML / and windows Batch file to compile to AIR 3.1
- That Batch file include an <ID> tag which was just a tiny little bit different to the one specified in iOS Developer Portal / iTunes Connect - and that breaks the verification process in App Loader
So moral of the story is: Make sure that
iTunes Connect Bundle ID = iOS Developer AppID (without the first 10 or so digits) = CS5.5 Publish Setting - Deployment - AppID
Or loose lots of sleep :-)
I've spent many hours creating and revoking certificates today because I couldn't upload to the App store through application loader. The ipa distribution files always installed to my iPad but would not be accepted for review. Finally, I came across this post and followed your video tutorials. I can't believe it but this time my app uploaded. Here's my question. Since uploading the app, I decided to test the app once again on my iPad with the new certs and provisioning profiles. I was able to get the app onto my device using the development cert and profile but NOT with the distribution cert and profile. Now I'm worried that the app I uploaded will have a problem. Do you know why an app would be accepted for review but not be able to install onto my device? It's weird that all of the earlier failed distribution apps would install to my iPad but didn't pass application loader. Any thoughts?
When you sign an app for distribution you can't easily install on your
device to test with. Technically you can go through a commandline
process with Xcode tools to get it to install, but once it's signed for
distribution, don't worry that it doesn't install. If you've tested the
app with the developer signing, and everything works as planned, then
the final app should be fine. Besides, Apple will certainly tell you is
something isn't right with your app.
Thank you so much! I suppose I can stop worrying and get some sleep tonight. What an ordeal!
Your videos are terrific. I can't thank you enough.