application failed codesign verification - solved issue
Hey all, I just spent many many hours trying to figure this out, so thought I would share what I finally figured out, and hopefully save someone else from the frustration.
I finished my iOS app using Flash CS5.5 air 2.6, and wanted to post it to the app store. It worked fine on iPad's, iPhone's, and iPod touch's using the development certificates and provisioning profiles. When trying to upload it using Application Loader, though, I kept getting the error "application failed codesign verification...". It didn't give me information to try and guess what might be going on, which was incredibly frustrating. I must have tried a hundred different variations on creating keys, creating certificates, creating app ids, creating provisioning profiles, etc.
for reference (again, for others having this problem reading this), common issues that I saw on other posts when you get this error are using development provisioning profiles instead of distribution, development certificates instead of distribution, or not using the correct settings when publishing in flash. Make sure in the deployment tab in iOS settings in flash cs5, you have the correct distribution certificate and distribution provisioning profile - not development - and that the app ID under the provisioning profile (e.g. com.mycompany.myapp, without the numbers in front) matches the bundle id in iTunes connect, and that you are set to publish as Deployment - Apple App Store at the bottom.
In the end, here are some things I was wondering might be the mysterious issue, that are ok to do
-- you can use OpenSSL to generate all the certificates and keys you need, publish with flash on a PC using those files, then move the file to a mac to use with Application Loader
-- you don't have to unzip the ipa file anymore (some posts I read say that you used to need to unzip it, then re-zip the folder within the ipa file)
-- Apple's procedures for checking codesign verification were not helpful. They indicated problems that in the end weren't really problems. They don't really seem to work on a non-xcode based app (I was getting desparate, trying everything I could to figure out what might be the issue).
-- I'm still not positive how careful you need to be, when creating your key with OpenSSL if you use the correct CN and email address, but that didn't seem to be my problem in the end.
to get all the files you need, I basically followed the instruction here
even though it isn't for flash, the provisioning and certificate stuff is the same.
so... the thing that was keeping my app from successfully uploading was the name for my .fla file. That is a pretty lame place for it to fail, and even worse that a simple name matching created an error that makes it seem like the keys and provisioning had a problem. I had made sure my app name within the settings within Flash matched the name on iTunes connect. I even unzipped the ipa file at one point, and changed the name within to match the name on iTunes connect (which was a pretty close guess). I guess that name propogates in the ipa file structure somehow, such that you have to make sure the file you even use to open your flash document, unrelated to specific settings within flash, needs to match your app name.
Hope that saves someone else the frustration I had. Hopefully my app is out next week (a kids Customizabooks book app, I'm Scared 
)
thx
tomlucient.
AdChoices