Has anyone seen this message....

bajash

Unable to authenticate the package: 123456789.itmsp

Can anyone tell me why this would happen?

Braydon_SFX

From what I've read, I believe that is an error that is given when publishing. I've read that you can just disregard that error and publish as you would. No need to worry about it.

jonmulcahy

Click on the activity button to get more details on why it failed

bajash

Thanks

LumpApps

Thanks, just got it to and will ignore. BTW where did the list of provisioning profiles go in Xcode 5? @-)

bajash

Ignoring does not help. It will not upload.

bajash

I looked up activity and this does not help either. I went to the developers forums and seems that this is a problem more than a few people have. Here is one of the answers:

"If you're submitting using Application Loader, you need to ensure you're sending the .ipa or .zip containing your compiled, signed application. Nothing else. Your .app should also be at the top-level of the archive, or within a Payload directory if you're submitting a .ipa. You should not have to create one of these yourself, you should use Xcode to build it and prepare it for distribution."

I can not figure out what this means. Any help out there?

jonmulcahy

like i said before, Click on the activity button to get more details on why it failed. you haven't done that yet. the activity button will give you a detailed message on what failed.

bajash

Yes, I did do that. The message I received was that the "codesign failed". I signed the app in GS without a problem. Not sure why I would get this message.

jonmulcahy

could you post the entire error message?

bajash

ERROR ITMS-9000: "Invalid Code Signing. The executable 'myapp.app/myapp' must be signed with the certificate that is contained in the provisioning profile." at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)

jonmulcahy

it looks like your certificate and profile don't match. I'd recreate your provisioning profile and try again.

bajash

will do and I will post follow up.

bajash

Did not work.

bajash

Follow up: I tried signing with another certificate and recreated provisioning file. That worked.