Skip to main content
C
CathyKeyBC
Participant
January 17, 2014
Question

Invalid signature error on submission to iTunes connect

  • January 17, 2014
  • 3 replies
  • 2043 views

I'm at the hair-tearing out end of stuck. Any help would be greatly appreciated.

I've developed an app using Flash CC configured to deploy on AIR 3.8 for IOS. Now I'm stuck on the final hurdle: submitting the app to iTunes connect.

I successfully uploaded the application - aside from some warnings about icons of size 120, 76 and 152. And then, immediately after I get an email that reads as follows: -

Invalid Signature - Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

I've checked, re-checked and double-checked again the certificate.p12 and the provisioning profile. They all look good to me, set to distribution not 'ad hoc'. The deployment type is set to 'Apple Ap store'.

Any ideas?

This topic has been closed for replies.

3 replies

Colin Holgate
Colin Holgate
Inspiring
January 17, 2014

By the way, you should use AIR 3.9 or 4.0, and add the new icon sizes to your XML. Those are required now (or at least will be on Feb 1st), and if you get past the certificate issues you might end up with the app rejected anyway.

User Unknow
User Unknow
Legend
January 17, 2014

Firstly download and configurate latest adobe air sdk http://www.adobe.com/devnet/air/air-sdk-download.html

3.8 realy realy outdated...

C
CathyKeyBCAuthor
Participant
January 17, 2014

I've uploaded the lastest air sdk (thanks, good suggestion). I'm certain I'm using a distribution P12 file (i've triple-checked against Keychain).

And, I'm still hitting the same wall.

Colin Holgate
Colin Holgate
Inspiring
January 17, 2014

What is the app id in Flash? What is the app id that the distribution App Store provisioning profile is based on? Does the provisioning profile have the same certificate embedded that your P12 is based on?

If you had a subscription renewal since installing the certificate you could end up with an issue.

Colin Holgate
Colin Holgate
Inspiring
January 17, 2014

From what you say the most likely thing is that the certificate P12 file you are using is a development one, and not a distribution one. You can’t tell a difference inside of Flash, you just have to make sure you’ve done all the steps up to adding the P12 correctly.

If you’re on a Mac, open Keychain Access. Click on My Certificates, and look for the iPhone ones. Make sure that you export the P12 from the Distribution one and not the Developer one.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices