Titanium Community Questions & Answer Archive

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

Not finding Apple Developer Certificate

My Titanium Developer 1.2.1, Titanium SDK 1.4.2, Project Test&Package View, is not finding my apple developer certificate. Yesterday it found the Apple Worldwide Developer Relations Certification Authority certificate, and my provisioning profile, but today it cannot find anything.

I have deleted and re-downloaded certificates and profiles, and uninstalled and reinstalled Titanium, in various orders, so I probably messed something up.

Thanks in advance - any help is appreciated.

— asked November 19th 2010 by Stan Silver
  • certificate
  • developer
  • iphone
  • mobile
0 Comments

2 Answers

  • Accepted Answer

    I've had similar troubles, and like Josh I've gone to building with xcode rather than Ti Developer. You can double-click your project in the organizer. In the list of build properties, set Code Signing Entity to your developer identity and the "any ios device" line to your distribution profile. You might want to make sure the Base SDK setting is at iOS Device 4.1 and not 4.0 also. Close the properties and build your app.

    — answered November 19th 2010 by Tim Poulsen
    permalink
    0 Comments
  • In my opinion, I wouldnt use Titanium for building the apps. It's dog slow, and normally doesn't work.

    Instead, just open your project in xcode (it will be in build above the Resources directory, then in the iphone subdirectory).

    To put it on your device, just go to Project->Edit Active Target "ProjectName", (you'll most likely be under the Release project settings)and under BaseSDK at the top, change it to iOS device 4.1 (or whatever version you're running). Change it from Simulator to Device, then build and run, and it will install.

    — answered November 19th 2010 by Josh Lewis
    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.