Skip to main content
Some_Dude
Known Participant
Feb 6, 2015 6:32 AM UTC
Answered

ITMS - 90179 Invalid Code Signing / ITMS - 90209 Invalid Segment Alignment

I've been getting these two errors no matter what I try. I've deleted all my profiles and certificates, remade them and even remade the App ID multiple times and nothing happened and still the same error. I've updated XCode too and still the same errors.

I used a Wildcard App to create my .ipa file in Flash Pro CC selecting the Apple App Store and tried to publish it through application loader.

Is there any solution to these two problems? Thanks.

This topic is closed to new replies. Start a new post to keep the conversation going.
Colin Holgate
Colin HolgateCorrect answer
Inspiring
Feb 6, 2015 2:02 PM UTC

If you mean you use a wildcard app id, that's something you can't do for the store submission. The provisioning profile and the app id have to be full, and the same as each other.

18 replies

Inspiring
Feb 18, 2015 10:15 PM UTC

Exports the p12 from Xcode was the only way I could get mine to upload -

Translate
Participating Frequently
Feb 12, 2015 4:07 AM UTC

Just tried out the latest SDK 17 released today, using Flash Builder and I'm still unable to submit my app.

I have published and updated apps in the past, I understand how certs/keys/profiles work. This error is just really weird!

Has anyone been able to submit a iOS 64 bit with Air 17 or 16 yet over the past 2 weeks?

Translate
Some_Dude
Some_DudeAuthor
Known Participant
Feb 12, 2015 7:16 AM UTC

Please tell me if you find a solution.

Translate
Participating Frequently
Feb 12, 2015 9:03 PM UTC

So today I tried resigning the same IPA with the same provisioning profile as explained here:

build - Re-sign IPA (iPhone) - Stack Overflow

Now I get another error when submitting #90166

Anyone ever ran into this problem?

Translate
Colin Holgate
Colin HolgateCorrect answer
Inspiring
Feb 6, 2015 2:02 PM UTC

If you mean you use a wildcard app id, that's something you can't do for the store submission. The provisioning profile and the app id have to be full, and the same as each other.

Translate
Some_Dude
Some_DudeAuthor
Known Participant
Feb 7, 2015 12:55 AM UTC

Well, I'm still getting the same errors after switching to explicit app id. Is there any idea on how to resolve this error? Thanks.

Translate
Colin Holgate
Inspiring
Feb 7, 2015 4:58 PM UTC

Which version of AIR are you using? I think there was a segment alignment issue that was fixed a while ago.

Translate