I know this is probably a long-shot, but I’ve had a few times where my certificate issues get resolved by doing this.
Start Xcode. Select Xcode->Preferences and choose Accounts.
Select your Apple ID and click the “View Details” button.
Click the Refresh button in the lower left of the dialog sheet. Wait for it to complete… and click it…again.
This procedure seems to sometimes refresh things in a way Xcode likes. Maybe worth a shot unless you’ve already tried…
Yeah already tried that was one of the first things I tried 
I have tried just about everything I can think of, so just cleaned up all my old certs, profiles etc. and currently format / re-installing a fresh copy of mavericks and see what happens with that lol…
This apple is only used for publishing with corona so re-installing isn’t that big of a deal
The only thing I can think of at this point is there is something goofing with xcode/corona because I can use the exact same cert/profile via xcode with just a simple hello world build “from objective-c” not via corona and it works perfectly.
I did also try with IOS7/XCode 5 and the cert and profile worked fine via corona on that as well, it seems to only be happening on IOS8/XCode 6
Yeah I thought you had most likely tried that already… Bummer…
Since I have Enterprise I always compile my Corona apps within Xcode. I’ll have a look at the app bundle that’s created by Corona and compare it with a native Xcode bundle and see if I spot anything unusual…
Thanks
I will also report back after this machine finishes its reinstall
Nope. I can’t find any weirdness in the app bundles between an Xcode and Corona build… 
Ok now I am going to have to figure out what is really going on…
A fresh install of OSX and XCode resolved all issues with the exact same certs/profiles.
So I am going to have to compare the backup to current to figure this out as even know everything works now and can upload etc. and so forth it is still annoying me lol
Great to hear that you got it working!
Now I just got to figure out what was actually the problem lol, its going to keep bugging me
There are too many causes of this to say “That was the cause” as an answer for everyone.
I’ve seen an expired certificate/key pair in Keychain Access cause this even with a valid pair there. You have to make sure to clean the Keychain Access out when you update your keys/certs.
I’ve seen people who put a bundleID in their build.settings forget that it’s there and then build against a different provisioning profile cause this.
I’ve seen people output their app build to their project folder. I’ve seen people with folders named Res or Resources cause it. Having an Icon on the OSX folder triggers that error. Engineering has been working to harden up this block of causes. Most of them should be addressed in the latest daily build.
Trying to make any edits to the Info.plist after the app is built will cause this error too.
Rob
I keep getting this 9000 error and I’ve made certificates, provision profiles, you name it, I’ve done it 10 times a piece. What am I doing wrong??? This is not my first app either. I’m using latest daily build 2512 and Xcode Version 6.1 (6A1052d). Using application loader 3.0. PLEASE HELP.
please post the full text of your message. All Apple submissions errors are 9000 errors.
oops! I forgot to add the screenshots on last message.
Also post your Corona SDK build screen just before you hit the “build” button.
Thanks
Rob
Xcode can be very picky with Code Signing Identities. You have a few expired ones that I’d highly recommend deleting.
They might be interfering with the new one you have created.
Your profiles are full of expired and invalid profiles. I would clean out your ~/Library/MobileDevice/Provisioning Profiles/ folder and download new ones. You also seem to have two Xcode identities present too.
In addition here are the list of things that have caused signing errors:
Expired Key/Cert pair in Keychain Access. Sometimes they are buried in side other entries.
Spaces in the path name (which you do have)
Icons on your folder (including coloring your folder), there will be an Icon? (really Icon\r) folder in with your main.lua
Using a res or resources folder.
Non ASCII characters in the project name.
etc.
Rob
There is a Library folder in your home directory. Inside of there is a folder called “MobileDevice” and then inside there “Provisioning Profiles”. Empty that folder and re-download your good ones.
From the terminal/command line:
cd ~/Library/MobileDevice/Provisioning\ Profiles
rm *.mobileprovision
Using Finder, click on the Go menu at the top, the “Go to folder” and enter: ~/Library/MobileDevice/Provisioning Profile
Move the profiles to the trashcan.
Redownload.
Thanks guys for the heads up… it was a bad certificate somewhere, I think I missed one when I tried to delete only corona certs. I erased them all, and it uploads fine now!!!
hello Rob, last time i submitted my build,
i got warning from apple saying
“WARNING ITMS-9000 missing 64-bit support. starting february 1, 20145, new ios apps uploaded to the app store must include 64-bit support…”
is there any news from corona to prevent this?
As of 2/1/15, Apple will require that apps support 64 bit slices. Today, Corona SDK and company only supports 32 bit slices. This is a hard engineering effort to address. It will not happen in the next public build which we are getting close to. Since our public builds come out on a 3-4 months schedule, it will likely be fairly close to this 2/1/15 date before this is handled for public builds. It will happen sooner for daily builds, but I don’t know when or how long this will take.
As of now this is just a warning. Engineering is aware of it. You can ignore it.
Rob
I keep getting this 9000 error and I’ve made certificates, provision profiles, you name it, I’ve done it 10 times a piece. What am I doing wrong??? This is not my first app either. I’m using latest daily build 2512 and Xcode Version 6.1 (6A1052d). Using application loader 3.0. PLEASE HELP.