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

Jul 11, 2008 5:43 PM in response to LaytonDuncan

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

The problem I had was white space. My program was in a directory that was named "MyExample - Example" and this was the app name as well. After changing both of these to not contain any white space ("MyExample-Example"), I was able to upload my app.

Hope this helps someone.

Jul 11, 2008 7:13 PM in response to kiichi

I'm not sure if this is your problem, but hopefully it helps someone:
I had a problem with invalid binary with one of my apps, even though I had done what it said. In the config part (where you change iPhone Developer to iPhone Distribution), I right clicked and selected "Show Definitions". This revealed that even though I had changed it in one mode, the change to "iPhone Distribution" had not taken hold in this other mode...I edited the value in this mode, and it worked.

Jul 13, 2008 6:53 AM in response to kiichi

I had the exact same problem and tried your potential solutions and many others. After a few hours and a night of thinking I stumbled upon something that worked.

My initial application was submitted prior to the final release of the iPhone 2.0 OS. Like you found, subsequent attempts to submit an updated application using the same distribution settings resulted in the error you described. After re-reading Apple's distribution documentation I noticed a new emphasis on wild-carded APP IDs. This emphasis did not exist when I first submitted my application so I did not use a wild-carded APP ID. So, I created a new APP ID with nothing more than an asterisk for the bundle identifier. I then created a new distribution provisioning profile for this APP ID and used it to sign my updated application and it worked! The upload was then accepted through iTunesConnect.

A few things to note:
1. Although you change the bundle identifier of your APP ID, you probably do not want to change the bundle identifier in your application's plist file. Although I don't know for sure, I'm guessing that it may be interpreted as a different application if the plist's bundle identifier changes.
2. When I say it worked I'm only referring to getting the binary upload to succeed. My application is still in review so I can't promise that something else won't crop up.
3. I am certainly no authority on this subject. Hopefully what has worked for me will work for you too.

As reference, you may be interested in reading pages 17 and 37 (assuming the document isn't updated) of the iPhone Developer Program User Guide. They talk a little bit about the wild-carded APP IDs.

Jul 14, 2008 9:53 AM in response to kunklejr

Thanks!

"Wild card for distribution" method works and it's "in review" status now! (It took 10 minutes to change the status after uploading via Application Loader)

As kunklejr mentioned, we are not sure this is right way, but as far as I see the latest version of the instructions at program portal, it says:

Prepare App -> 2.5

Select your wildcard App ID to build all of your applications with your single Distribution Provisioning Profile.

OK... I thought that I have to make my app id really unique, so I put like com.companyname.appname but now it's just an asterisk.

Anyway, my application got in the next stage, and my ticket is still open, so I'll update status once it's approved / rejected.

Let me flag this thread as "Answered" if it's approved.

Thanks again!

Jul 14, 2008 9:58 AM in response to kiichi

Just additional things that we've found:

Once you build your binary, right click on .app -> select "Show Package Contents". I noticed that our icon file is corrupted. the file name was "57x57.png", but when I changed it to "icon.png" it did not corrupted. I guess it does not take file name starting with number?

I did not get any image validation error but I needed to remove all possibility of failure.

This technique might be useful to investigate inside the release package.

Jul 26, 2008 8:17 PM in response to kiichi

http://forums.macrumors.com/archive/index.php/t-518011.html

gralem said it best and fixed my issue when I had to update my application:

VERY IMPORTANT: When building your app for the App Store, it can be very easy to forget to Set Active SDK->Device. If Active SDK is left on Simulator, you cannot upload the resulting application to the store. When you want to upload to the App Store, set SDK to DEVICE!

After that, I was able to re-sign my application, compile it, and upload it without a hitch to the App Store as an update. Thanks everyone!

Aug 27, 2008 2:35 AM in response to BeyondtheTech

FRUSTRATED....

After having the same "Waiting for Upload" problem as others, I have done the following:

- Removed all spaces from any paths, names, bundle, app, icon, etc...
- Renamed my icon file to icon.png
- Checked the file with codesign
- Uploaded, and uploaded some more....

NOW, I get a response from apple that the Zip File Structure isn't correct. Following the instructions, I right-clicked on the .app and compressed it. The resulting zip file has only the app bundle inside. I have no idea how to go forward.

Also, can someone point me to an explanation of the relationship between the AppID, Name, Company Name, and Bundle Identifier?
I'm running out of other options, so it must be something in this area.

If I use com.mycompany.${PRODUCT_NAME:identifier} as the bundle identifier, what should be in the fields above??

Aug 27, 2008 10:27 PM in response to tsayman

I finally got my app uploaded, but it took 2 days of hackin' & slashin' 😟

Not counting the aggro I had to get the app store distribution cert selected (Common Name confusion), I reached the point where the upload failed with complaints about my bundle identifier.

I fixed those by making sure there were NO underscores, spaces or dashes in my product name, nor in the bundle identifier itself, nor in the directory path to the .app package file.

So, that got me to the same point as the OP: a failure to upload my zip file with an error message complaining my app wasn't signed with an Apple submission certificate (emphasis on submission lol... never mind).

I did a 'Show Package Contents' on the .app file, and sure as boots it was missing the embedded.mobileprovision file which is where the digital signatures are kept! What gives?

Doing a Clean and Build THREE times in succession (with no tinkering in between - honest!) finally produced a digitally signed package. It seems almost arbitrary and inexplicable.

Anyway, compressing that last .app package finally uploaded happily, but man... what a process!

Sep 20, 2008 7:08 AM in response to smartsoftwaredevelopment

Hi there Eugene,

This thing is my current nightmare - The error message on iTunes Connect saying that - 'The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate. '


I am unable to upload my app...And i have done it all..changed the ocnfigurations and new settings and new profiles and entire fresh project environments (tried almost 3 of them)..But the error does not go...

I read your post regarding the codesign -vvvv thing and i get the message -

y-kamesh-raos-macbook-pro:~ ykameshrao$ codesign -vvvv ~/Desktop/Umundo.app
/Users/ykameshrao/Desktop/Umundo.app: a sealed resource is missing or invalid
/Users/ykameshrao/Desktop/Umundo.app/._Entitlements.plist: resource missing


How do i fix this issue..
I already tried creating new entitlements.plist file and clean build and everything....my build log states -

CodeSign "/Volumes/DATA HD/Source/IPhone/Umundo DT/build/Distribution-iphoneos/Umundo.app"
cd "/Volumes/DATA HD/Source/IPhone/Umundo DT"
/usr/bin/codesign -f -s "iPhone Distribution: Umundo" "--resource-rules=/Volumes/DATA HD/Source/IPhone/Umundo DT/build/Distribution-iphoneos/Umundo.app/ResourceRules.plist" --entitlements "/Volumes/DATA HD/Source/IPhone/Umundo DT/build/Umundo.build/Distribution-iphoneos/Umundo.build/Umundo.xcent" "/Volumes/DATA HD/Source/IPhone/Umundo DT/build/Distribution-iphoneos/Umundo.app"

Can you point the error or some way on how to fix this...

Nov 8, 2008 5:00 AM in response to ppinter1

I still can't get past this part of the process. I keep getting the invalid signature error on my first upload. I have gotten rid of spaces in the app name and in the path, I have check with the "codesign -vvvv myapp.app" command and gotten back the expect "valid on disk / satisfies its Designated Requirement".

I have looked at the build detail and it is using my distribution certificate.

The only thing I can think of is the bundle id in my plist being bad. I am using this:

I would try the Application loader but I have tried to download the application loader 10 times and it always stops partly through for some unknown reason.

Bundle Identifier: com.exambusters.${PRODUCT_NAME:identifier}

Bundle name: ${PRODUCT_NAME}

my product name is "Algebra1"

Any help is greatly appreciated, I sure wish they had better diagnostics in the upload. There may be 10 things they are checking for, why not just list them one at a time, with checkboxes, so we don't have to waste our lives trying to figure out some tiny problem.

Nov 20, 2008 3:59 AM in response to hard_wurker

Guess you need to explicitly specify you Bundle Identifier (ie. com.exambusters.Algebra1).

Me too, have some problem with uploading app to iTunesConnect. But I've managed to figure all the problems out with a lot of help from this thread. So, this is my contribution back. ;D

- After built your app, always check the build result. If no mobileprovision file part showing, clear all build target and re-build again.
- Immediately zip your .app file after build. DO NOT USE THE "SHOW PACKAGE CONTENTS" menu in finder. It will break the codesigning.
- No space, under scroll or other special characters in Bundle Identifier. Stick with letters and numbers.

Hope this help someone.
Cheers

Message was edited by: s.narut

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.