User profile for user: kiichi
kiichi Author
User level: Level 1
0 points

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
Question marked as Top-ranking reply
User profile for user: kunklejr
kunklejr
User level: Level 1
10 points

Posted on Jul 13, 2008 6:53 AM

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.
View in context
53 replies
User profile for user: kiichi
kiichi Author
User level: Level 1
0 points

Jul 9, 2008 8:36 AM in response to smartsoftwaredevelopment

Thank you for the verification method, I did not know this tip. This is the console output result:

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

It run at MyApp/build/Distribution-iphoneos/
and the command exactly you provided: codesign -vvvv MyApp.app

It seems that the messages are ok? Did it give you some kind of "invalid" in your case?
Reply
User profile for user: barneybarnesbear
barneybarnesbear
User level: Level 1
0 points

Jul 9, 2008 12:34 PM in response to kiichi

I have been having the exact same problem and mine also passes the codesign check. When I use the application loader it does the same thing yours does. I think the only thing I am doing differently is uploading my second app and not an update.

I was able to submit my first app last Thursday which was already approved so this is starting to get frustrating after about 12 hours of trying. I have even totally rebuilt the whole app with the source copied into a fresh project but get the same behavior. I have reinstalled my certificates more times than I can count. I am totally out of ideas so if you figure anything out feel free to share.
Reply
User profile for user: tsayman
tsayman
User level: Level 1
1 points

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??
Reply
User profile for user: Shaheer
Shaheer
User level: Level 1
0 points

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...
Reply
User profile for user: hard_wurker
hard_wurker
User level: Level 1
25 points

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.
Reply
User profile for user: Doug Lerner2
Doug Lerner2
User level: Level 4
1,388 points

Mar 13, 2009 9:18 PM in response to songuke

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
Reply
User profile for user: Doug Lerner2
Doug Lerner2
User level: Level 4
1,388 points

Mar 15, 2009 6:05 PM in response to vpMobile

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
Reply
User profile for user: iMarek
iMarek
User level: Level 1
0 points

Mar 23, 2009 4:31 PM in response to Doug Lerner2

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.
Reply
User profile for user: parislee
parislee
User level: Level 1
0 points

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.
Reply
User profile for user: parislee
parislee
User level: Level 1
0 points

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
Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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 Account.
Learn more Sign up