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

Top-ranking reply

kunklejr

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

Jul 9, 2008 8:12 AM in response to kiichi

I believe I saw on the App Store WWDC video, that when you update your application, the App ID needs to be exactly the same as the previous version. This is because it is replacing the old version, and is a way to broadcast the update notice to all that bought/downloaded your program.

Jul 9, 2008 8:17 AM in response to kiichi

I had the same problem. It means that for some reason, your app was not signed with a distribution profile at all.

Use a terminal window and go to the directory where you have your .app. There do "codesign -vvvv AppName.app", where AppName is the name of your .app. What output does that give? It will tell you that it is not signed, right?

Build everything again until you can get it to be signed and then submit again.
Eugene Vassiliev
Smart Software Development

kiichi Author

Level 1

0 points

Jul 9, 2008 9:12 AM in response to smartsoftwaredevelopment

Thanks, I downloaded Application Loader, and it uploaded without error! I got the Thank you screen with Successfully uploaded message.

I'm looking at iTunesConnect's manage application screen, and it is still saying

Status: Waiting for Upload

Does this take time to change? I'm just worry about it might get same error somewhere behind. I'll wait for half hour.

TW83

Level 1

0 points

Apr 20, 2009 4:24 PM in response to kiichi

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.

tux0010

Level 1

0 points

Jan 26, 2009 8:45 PM in response to songuke

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.

lcukyapp

Level 1

0 points

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.

Jul 9, 2008 8:52 AM in response to kiichi

Hmm... It looks just fine.
If an app is not signed, it will tell you that the file is not signed.
Try uploading with Application Loader. It works as well, sometimes even better. Your app doesn't have to be large to use the Application Loader.

I am suggesting that because Application Loader gives different error messages, sometimes more detailed.

Eugene Vassiliev
Smart Software Development

Mar 23, 2009 4:50 PM in response to iMarek

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

kiichi Author

Level 1

0 points

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.

Jan 30, 2009 10:50 AM in response to BeyondtheTech

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!

May 4, 2009 2:36 PM in response to Doug Lerner2

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....

Jan 11, 2009 12:17 PM in response to kiichi

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.

Jul 9, 2008 10:02 AM in response to kiichi

If the status remains "Waiting for Upload" for more than 30 minutes, it is likely there was another problem with the binary. You see, Apple has automatic checks in place that won't make the binary available to their review department if there is something wrong with it. You might expect an email from an iTunes Connect engineer soon, just like it was in my case. He will tell you what needs to be fixed. It might be sent to your iTunes Connect management email or the tech support email you specified in meta data. Please check both.

Eugene Vassiliev
Smart Software Development

kiichi Author

Level 1

0 points

Jul 11, 2008 6:46 AM in response to fasttech

OK, this is what I got.

Thank you for contacting the Apple Developer Connection regarding the issues you've
experienced when attempting to upload your app to the App Store via iTunes Connect.

We ask that you please use the following troubleshooting information to assist in re-attempting your upload:

Your Info.plist must list your icon file with the proper .png extension. If your
file is listed as .tiff, please update to .png

Ensure that your icon file is the correct file size. The large Icon should be 512x512 and the
small icon should be 57x57

Ensure that you have a valid bundle identifier

Detailed informaiton regarding the Upload page and uploading applications via iTunes Connect
can be found in the iTunes Connect User Guide which is posted on the iTunes Connect site.

If you continue to experience an issue wtih your upload, we ask that you please let us know so that we may further assist you. We would ask that you include the specific name of your application in your response to expedite this process.

-----------------------------------

I concern about "valid bundle identifier" and my info.plist shows

com.mycompany.${PRODUCT_NAME:identifier}

but this value never changed since I uploaded the first version.

Message was edited by: kiichi

kiichi Author

Level 1

0 points

Jul 9, 2008 8:31 AM in response to seahorsejl

Hi,

Thank you for advice, Originally, I tried with same provision file which uses same appid, then I just tried with new provision file with new app id. Neither of them did not work.

I will double check my provision & app id with the original one.

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