I have a number of apps that are almost identical (with the exception of a few constants, images, and a sqllite database file). I've never had any issues submitting them before, however today one of the updates gave the following error when validating/submitting (note: I have updated this app in the past with no issues):
Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate.
I've spent all day trying everything to get this to work. I even diff'd the entire project folder against another app (which submitted successfully, today), and all build/signing settings are exactly the same (except bundle identifier, version number, etc.). I've even (as a last resort!) revoked the certificate and re-generated everything, including provisioning profiles.
I've been through all of the steps listed here:
However, if I "Share" the app from the Organizer and save to disk, running codesign -dvvv says it's not signed at all (however, this happens with the ones that worked!). Not sure how else to run this, as the file generated (and shown in Organizer) is not a .app file.
I'm at a total loss how to figure out what's wrong with this, or why it's any different to the others. I don't seem to be able to get any more information out of the Organizer. The app was built exactly the same way as the others, and the project files etc. are identical (except for expected differences like images/names).
Ok, fixed this... I wish I'd tried this sooner, as it would've saved me many hours today!
It seems that the App Store provisioning file for this app was somehow corrupt - not on my Mac, but on Apples servers.. I downloaded it many times today, with no luck. I just discovered that selecting the Ad-Hoc profile during Validation worked, which led me to believe it was specific to the App Store one. So I deleted the App Store provisioning file from the iOS dev dashboard, then recreated it, downloaded it, and it worked!
Before I deleted it, I edited it, and everything was set correctly, and the expiration date was 6 months from now, so I can only assume something was broken Apple's side (even though I'm sure this same file worked in the past!) :-(