Well, I made it this far, and am trying to submit the app to iTunesConnect, but I'm having a problem with the Distribution Certificafe...no private key :-) So, I delete it both from the Mac/Xcode and developer.apple.com and recreated it, but same error. I tried following steps at http://www.raywenderlich.com/8003/how-to-submit-your-app-to-apple-from-no-account-to-app-store-part-1 So, my questions: - are you supposed to use the same csr generated for the Development Certificate for the Distribution Certificate (I assume not). Application Loader wanted to create the Distribution Certificate for me, but was asking for a password which didn't work (been a while, so not sure if I specified a different password for the Development Certificate). - I tried creating a new Distribution Certificate (and uploaded the csr from the Mac as part of the process), but still no private key. - should I just delete both the Development Certificate and the Distribution Certificate and just recreate both? The Development Certificate works fine as I've been using that to test on my iPhone/iPad. But I can't submit to iTunesConnect without a proper Distribution Certificate. Why does Apple make this so convoluted? LOL. Any suggestions welcome. Thanks!

In a nutshell: Download the Apple 'public' certificates. Install them in your keychainaccess.app Create a CSR with your keychainaccess.app for use as your 'Developer' credentials. Request, and install the certificate that is associated with that CSR. You no longer need the CSR. The certificates you install should have both developer and distribution certificates, and should be guarded by a private 'key'. (see https://dl.dropboxusercontent.com/u/115208762/AppCertiOS.pdf for an example) Create an App Bundle ID in your Developer Account Create a Provisional Certificate request based on that Bundle ID. Add the devices you want to test with. You can request both developer and distribution certificates. Install the Provisional Certs. That sort of should be all there is to it. If I am building an app 'for me', I login to my dev account as 'me' and it references my 'credentials' for this computer. If I am building an app for 'the company' then I login to my dev account as the company, and it references 'company' credentials... It kind of 'is' a pain to get setup, but once it's setup, it's fairly generic. Hope you get through it, and I hope this can help! Cheers! -- Smug Edit: Oh, and I don't want to sound silly or state the obvious, but I have seen situations where the developer's certificates expired and it drove them to tears before they discovered it. Just take a glance and make sure...

@SmugWimp. Thanks! I'll follow your steps...some of the steps I may not have to repeat, but will see. A couple of questions: - when you say "If I am building an app 'for me', I login to my dev account as 'me' and it references my 'credentials' for this computer." By "I login to my dev account", are you referring to logging into your computer? If so, what does that have to do with using your dev vs company credentials :-) - I already created the App Bundle and added devices to test with. As stated, I've been testing with the Development Cert on my iPhone/iPad. Should I still recreate the App Bundle to clean things up? BTW, my developer account WAS going to expire in July and I just renewed it last night...could that have anything to do with the issues I've been having with the Distribution Cert? Will try again on Saturday. Cheers Steve

Well, you get provided certificates for an 'entity'. With Apple, that entity can be either an individual or a business. The only real difference is the hoops you have to jump through to become a business developer. The biggest noticeable end result is that some apps say 'Clarence Fields' is the developer, and some apps (will) say that 'Marianas GPS, LLC' is the developer. At the end of the day, you're only going to have two certs for a single developer entity; a Dev cert, and a Dist cert. Both with a private key generated from your CSR. When I say 'I log in as me' or 'I log in as my company' this is something that only affects *me*, and all I'm doing is using different account credentials, which will alter which certificates are referenced. Sort of like 2 developers sharing the same computer. If you, as either an individual or a company only have one account, then you won't need to worry about it; I only mention it because I have two accounts, and it might be confusing for some if they expect a whole screen of certs; you won't, you'll only have two per account. Creating another 'App Bundle ID' probably won't matter. Creating a Provisioning Cert 'for' that bundle possibly could. Make sure it's a distribution certificate, and ensure that your app signing section reflects the correct certificate. I doubt if your dev account matters as long as it didn't expire. 'almost' shouldn't count. At least, I hope not. Since the whole developer process (at least visually) has changed a bit, I was using that opportunity to create a tutorial on it, but for the moment all I have are the screen shots... You're welcome to look at them, but I don't expect them to make total sense just yet... https://dl.dropboxusercontent.com/u/115208762/appledevcert.pdf Cheers! -- Smug

Ok, I guess the problem might have been related to fact my developer account was coming up for renewal. Distribution Cert generated/installed, app archive created, and app submitted to Apple for review. I logged into iTunesConnect and see that the In-App Purchase has also gone into PENDING status. I guess I gotta get cracking on finishing my support site :-) BTW, what's the average app size for people? Mine is about 18MB (it includes 3 image files, 3 sound files, and 7 launch screens for various sizes of iPhone/iPad for retina and non-Retina). Can't wait to see whether Apple comes back with request for changes :-) Wonder how long they take?

Hmmm...got the following cryptic warning from Apple...seems like there is a push API being used in the app that I may not be aware of...any ideas and whether I need to take any action? I wonder if this is related to Scringo which I added to the app? Should I enable push and resubmit the app? Cheers ------ Dear developer, We have discovered one or more issues with your recent delivery for "yyyyy". Your delivery was successful, but you may wish to correct the following issues in your next delivery: Missing Push Notification Entitlement - Your app appears to include API used to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. See "Provisioning and Development" in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API. If you would like to update your binary for this app, you can reject this binary from the Binary Details page in iTunes Connect. Note that rejecting your binary will remove your app from the review queue and the review process will start over from the beginning when you resubmit your binary. Regards, The App Store team

Well, my first app was about 3MB. the one I'm currently working on, which includes offline maps for my island from zoom levels 10-16 is about 10mb, and will probably get bigger. Best of luck on your submission! (figure around 7 days for a complete turnaround. rarely faster, sometimes slower) Cheers! -- Smug Don't worry about that 'cryptic warning'. Ever since BT implemented push, we all get that message. Basically all they're saying is 'hey, you've set this up for push, but you're not pushing. You know this, right??'. It's not a factor in your approval or denial.

Great, thanks! I'm just wondering now about the fact that the Weather app is requesting your location and if someone clicks "No" then they'll never get Weather in the app...I guess I should have included a settings screen for that...what do you normally do for that? Cheers

In your support site, mention that if they disable location services on startup, they can re-enable them in their device settings > location services. That's about all you can do. Cheers! -- Smug

Thanks Smug :-) I guess something to think about for version 2 as well :-) What software/theme do you use for your support site? I'm using WordPress and trying to get the theme right for the main page :-)