Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Invalid Signature Error when I update in app store

Hello,

I uploaded the first version of my app to app store, then I tried to update my app to next version. When I choose my app file in "Upload Application" screen, I got error about invalid signature as below.

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

Strange thing is I used exact same project configuration and machine when I uploaded the first one, but it will throw the error when I select the file.

I tried these things:
1. Create a new app id and provision file, and select the new provision file in target->Code Signing section
2. Changing Bundle Version Number in .pinfo file.

I'm trying some solutions people discussed here
http://discussions.apple.com/thread.jspa?messageID=7469931&#7469931

but I still get the same error message. Does anyone have advice for me?

iPhone

Posted on Jul 9, 2008 7:59 AM

Reply
53 replies

Aug 14, 2009 1:07 AM in response to gebitu

Just for the record and for other people. I was having the same issue while working on two apps in the same xcode project (lite & premium). I already had my lite app on the store. When I built it and uploaded it, it got rejected with the same message. Even stranger, when I compressed the app folder, it would sometime create 8KB zip files instead of hundreds of kB.
My bundle id hadn't changed, and the mobile provisioning thing was correct. Codesign was giving me the Go

Here is what worked for me
- clean lite target
- close all finder windows
- close xcode
- open xcode
- build lite target for device & distribution profile
- open finder and go to build directory
- compress folder
- upload -> it worked
- clean premium target
- close all finder windows
- close xcode
- open xcode
- build premium target for device & distribution profile
- open finder and go to build directory
- compress folder
- upload -> it worked

Failing to close the finder windows or xcode gave the same error messages.

Hope this helps someone as much as the previous messages helped me!

Aug 24, 2009 9:53 PM in response to watcherFR

Hi,

I have tried everything that you said and running the command as
codesign -vvvv myapplication.app

I got the the same result:

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

So, I should not have the "Signature Error", but I have tried many many times, build and rebuild. The same results.
Could you help ?

Thanks thousands times.

Aug 25, 2009 2:52 PM in response to kiichi

Hi,

I have read again and again all postings and following the [Distribution] all the links from [obtaining Distribution Certificate] to [Verifying Successful Distribution Build] and checking the build result in the [log] that
[embeded.mobileprovision] is in my [Distribution]folder and [codesign -f -s "iPhone Distribution: xxx" --resource -rules =...etc] using my certificate.
But when I uploaded with my .zip file, I got [Invalid Signature Error...].
Can someone help ?

Thousands thanks.

- Alex

Oct 19, 2009 3:40 PM in response to parislee

I didn't find the provisioning code from build results, but when i use terminal to test the .app file it was all fine. I couldn't done the submision with iTune connect, but i installed application loader and the .app file was uploaded fine. my app is under review now.

very strange and i don't really understand why iTunes connect reject while application loader can accept it.

Oct 26, 2009 12:11 PM in response to kiichi

I had the same problem and fixed it by copying my application directory from a network drive to the desktop (and rebuilding in xcode).

I only happened to find this solution through trial and error, it was not in the documentation and this error message is not very descriptive. It would be nice if Apple were to mention that the files have to be on the local machine (or perhaps just not on a Windows server).

Feb 28, 2010 4:56 AM in response to kiichi

I wanted to say that this thread really helped me out. For me, I had an ad hoc distribution profile and had to create a new App store one to attach onto my signing certificate. After downloading that and importing the new distribution certificate (it's a .cer file), I had to make sure the signing identities for both the project and the target were set to the new profile.

It helps to name the app store profile something recognizable.. like APP STORE DISTRIBUTION.

Also, I don't know if it made a difference or not, but close all my finder windows, cleaning, restarting xcode, and then building seemed to help.

Invalid Signature Error when I update in app store

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.