Invalid Signature Error when I update in app store

This is a very bad error message indeed. All I had to do to fix it was change the Icon.png size from 512X512 to 57X57 and it went away. Nothing to do with code signing.

Hi all,

I got the same error and overcame by this:
1. Ensure the provisioning profile is embedded into the .app package. This can be done by showing package contents and check for the embedded.mobileprovision file.

2. Someone has trouble with the bundle identifier (like me) can check this:
- Note that the com.yourcompany.{PRODUCT_NAME} will not work.
- The bundle identifier must be similar to the App ID on the Program Portal.
So what I do is go to the Program Portal, copy my App ID, something like BLAHBLAH123.com.mycompany.something. Just remove BLAHBLAH123 prefix and paste the remaining to the bundle identifier. Please note that the App ID (without prefix) must be exactly pasted to bundle identifier (with every fullstop, underscore, EXACTLY). Then it works. This is what I've been doing.

Hope this helps. 🙂

Dude! You're the best! I spent 2 hrs trying to figure out why I was getting the same error. The problem was the I had the BLAHBLAH. part in the Bundle ID. I removed it and now my binary uploads fine! Thank you so much!!

- Raja.

OMG, thank you BeyondtheTech, this issue has been a thorn in my side for 4 days. Why did Apple not mention that you needed to set it to the device and not the simulator? Seems like such a simple thing!

Thank You, Thank You, Thank You. Kiicchi, you have saved me another night of pulling my hair out, and cursing my machine. I just changed my distributor provision to one which uses a wildcard appID, while leaving the Bundle Identifier (in info.plist and the General settings tab in the Targets file) as an explicit value. To Clarify: I used a provision with the appID com.CompanyName.* and a Bundle Identifier of com.CompanyName.AppName - and viola! upload success. Not sure how it will work out upon hitting the review board, but will leave updates

If I look at the App ID in the portal it is just

BLAHBLAH123.*

My bundle identifier for my original app, which I am trying to upgrade, was

com.mycompany.${PRODUCT_NAME:identifier}

That was the way it was in there - literally. My original app upload worked just fine though and has been on sale since last September.

I was thinking I should change "mycompany" to my actual company name, but that didn't help either. I am still getting the dreaded

The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.

error.

I'm so stuck. I don't know what to try next.

From your explanation, it sounds like I should strip BLAHBLAH123 but then all that would get pasted in the Bundle identifier field would be

.*

That doesn't look like it would be right, does it?

Thanks,

doug

Is this suggestion still valid with .app files produced with the current SDK?

If I try

codesign -vvvv HelloWorld.app

(for example)

the message returned in the Terminal just says

HelloWorld.app: object file format invalid or unsuitable

doug

Never mind on this question. The command works. I was just pointing to the wrong file.

I still can't upload by app, but that command is reporting:

MyAppName.app: valid on disk
MyAppName.app: satisfies its Designated Requirement

doug

If you are like me and had the wrong Bundle Identifier in your first version back before they checked... don't fret, the old one will still work.
If you are still getting this error, right click on MyApp.app and select Show Package Contents. Most likely you will be missing the file embedded.mobileprovision even though the log file clearly shows it being written. The fix is simple... Close XCode, delete MyApp.App, launch XCode and build. The file embedded.mobileprovision gets generated and everything is fine again.

Thanks for your note.

However, as mentioned in my posting, I did Show the Package Contents and embedded.mobileprovision is there. I do that check for every app store build, as recommended in the manual.

If anybody is interested, I have complete screenshots and a list detailing all the steps I followed and can send a private email with everything - including a screenshot showing the Package Contents described above.

My email address is doug@lerner.net and anybody is welcome to email me if they are interested and can, hopefully, help.

Thanks!

doug@in despair

Hi there,
I was going through all your posts and couldn't figure out what to do with this: "The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate."

Basically I am submitting my App on iTunes Connect website. Provisioning Profile seems to be OK, Icon.png also, App ID as well, I have been even trying to create a new provisioning profile which then was rejected by my Xcode Organizer. So maybe really there is something wrong with my provisioning profile.

This is my first App though, worth to mention. Though I am seating on that already 6h and I am tired!

I do not know what else I can check, please help me on that if any one of you guys had the same problem.

Thanks in advance.

I did finally figure it out. In my case it was clearly an Xcode bug affecting older projects that haven't been updated in a while.

I posted my complete solution to this thread:

http://discussions.apple.com/message.jspa?messageID=9167082#9167082

It involves opening up the Xcode project package and doing an easy edit of a file inside the package remove a redundant line.

doug

Thank you thank you thank you!!!

I stumbled around for about 5 hours yesterday and today trying to figure out the root of my "codesign error". I ended up removing the XXXXXXXXX. from the bundle identifier and it worked like a champ on the first submission attempt after that.

I had the same problem and this is how I fixed it!

I changed the Bundle Identifier from :

com.mycompany.${PRODUCT_NAME:identifier}

into

com.mycompany.AppName


As long as the AppName is unique, meaning not being used by other apps you already submitted it should be ok.

It worked for me....

Bingo!

I had the same problem. It turned out that even though I was selecting "Distribution" for my build config, I had left "Active SDK" set to "Simulator - iPhone OS 2.0".

I changed it to "Device - iPhone OS 2.0" and the resulting built was accepted by iTunes Connect.