Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Application failed codesign verification

I'm trying to update an app that is already approved and in the app store two weeks ago. Last week when the 4.0 SDK came out, I installed that and have been unable to send updates using either iTunes Connect or Application Loader since. I have redownloaded and selected the distribution certificates to now avail. Other people seem to be having this problem as well. I'm using Titanium 1.2.1 and SDK 3.1 (should apps be built using the 3.2 final now?).
Does anyone have instructions to fix this or to completely uninstall Titanium and or the SDKs if that is the issue?

— asked April 14th 2010 by Troy Taylor
  • 1.2.1
  • 3.1
  • 3.2
  • application
  • certificate
  • codesign
  • itunesconnect
  • loader
  • uninstall
  • verification
0 Comments

5 Answers

  • I'm pretty sure that they (Appcelerator) haven't updated the Titanium tools to deal with the 4.0 SDK yet. Though I did read that they about to add that.

    Have you tried submitting with 3.1.2 or 3.1.3?

    — answered April 14th 2010 by Kosso
    permalink
    0 Comments
  • Yes, I've tried with 3.1 and 3.1.3, but I think this is a certificate issue. I really like a way to completely uninstall Titanium and all the certificates to know that I'm starting fresh (other than an OS reinstall which I'm thinking about).

    — answered April 14th 2010 by Troy Taylor
    permalink
    0 Comments
  • Got it working!! SDK 1.2 on iPhone 3.2

    I went though the same distribution painful ordeal yesterday, like yours, removed then regenerated certificate and distribution profile and nothing worked.

    This morning, i installed both Titanium & Xcode on a different machine. Create new project, copy all the files and recompiled, create new package then generate new Cert from the new machine, (just distribution cert, not development) went though the lengthy steps and voila. It submitted though.

    Couple things i should mention, i am using some user Apple Developer account to create the Apple's end cert and profile, but that didn't stop me from getting development part to work. It installed on device just fine. May be the Codesign failed on distribution level because of account validation choked? not sure.

    The new machine is belonged to the owner of Apple developer account however, with his name and everything. That's the first thing. The 2nd reason could be xcode failed to assign correct profile (search on goggle mention tons of this problem) or Titanium was to blame?

    So if all things failed, perhaps reinstall Xcode or Titanium could be your answer?

    — answered April 14th 2010 by Daniel Lim
    permalink
    0 Comments
  • Hi there,

    I'm sure I read that 4.0 is developer preview/beta, so wouldn't expect it to deploy, even if everything else was working. There are probably FAQs around this in the Developer portal.

    Apparently you can have iPhone SDKs 3 and 4 installed on one machine, but you'll need two separate installations in two separate folders - according to some posts in the Apple developer forum - may want to check there.

    cheers,
    Chris

    — answered April 14th 2010 by Chris Reed
    permalink
    0 Comments
  • I experienced the same thing after installing 4.0 SDK. Reinstalled 3.1.3 SDK and it codesigned and submitted successfully.

    — answered August 6th 2010 by bob hope
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.