Hi, I'm having problems. I get my uploaded app but then I get an invalid binary error message. I've done everything the message boards suggest. Clean all targets...ensure that the proper, valid (distribution) profile is selected in both the project AND the target. The bundle identifier is correct. I validate the archived build through xcode and it tells me it's valid and can be uploaded. I build for device configured for release (actually, for distribution, a copy of release that the apple developer site said to do (but just in case that was wrong, too, i built it configured it for release, archived, uploaded and still got the invalid binary message)). On some boards, i see a mention of an Entitlements.plist, but i don't see that file anywhere in the folders. Could that be the problem? Help please.

Hi. Invalid Binary issues are difficult. And, if you're doing this as a Distribution build (as compared to a release or debug build) things get even more complicated. Start here and see if this helps: http://stackoverflow.com/questions/47941/invalid-iphone-application-binary 100% of the time these issues are related to 'how' Xcode is signing your app. This type of problem has nothing to do with your project per se, only how iTunes Connect and XCode are validating your Apple credentials, provisioning profile, etc.

Thanks for the response David. I finally figured it out. The cause? I am not the Team Lead. I thought I could outsmart the system. I created the certificTw request, created a new distribution profile, downloaded and added the profile and certificate. My machine showed that I had the profile, the matching private key, and like I said above, the archived built file validated from the Organizer window. I think it validates because at that point, it's just checking to see if the profile matches the cert. (also I may have used the team lead's credentials, which let me in iTunes Connect when my own credentials wouldn't.) problem solved. Even though the team lead is in another city, he opened up the project, got a certificate he could use and bam--accepted the first time. Grrr. Guess I shouldn't try to outsmart Mr. Jobs.