Skip navigation
This discussion is archived

Invalid Signature Error when I update in app store

53338 Views 53 Replies Latest reply: Feb 28, 2010 4:56 AM by maeldur RSS
1 2 3 4 Previous Next
kiichi Level 1 Level 1 (0 points)
Currently Being Moderated
Jul 9, 2008 7:59 AM
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
  • seahorsejl Calculating status...
    Currently Being Moderated
    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.
    iPhone 8G, Mac OS X (10.5.2), MBPro
  • smartsoftwaredevelopment Level 1 Level 1 (10 points)
    Currently Being Moderated
    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
    Mac OS X (10.5.2)
  • smartsoftwaredevelopment Level 1 Level 1 (10 points)
    Currently Being Moderated
    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
    Mac OS X (10.5.2)
  • smartsoftwaredevelopment Level 1 Level 1 (10 points)
    Currently Being Moderated
    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
    Mac OS X (10.5.2)
  • barneybarnesbear Calculating status...
    Currently Being Moderated
    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.
    macbook pro, Mac OS X (10.5.4)
  • fasttech Calculating status...
    I am having the same problem. Please let us know if you get a response back from Apple. My app passed the codesign verification too.
    Mac OS X (10.5.1)
  • fasttech Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jul 11, 2008 7:45 AM (in response to kiichi)
    kiichi,
    Are people able to get your first version of your app in the App Store while you are working out the problem with your update? People that try to buy mine are saying that it says they can't buy because the app is being modified. Is this the same case as you?
    Mac OS X (10.5.1)
1 2 3 4 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.