IOS Standalone-error: "could not find a valid iden...[SOLVED

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

SusanB
Posts: 111
Joined: Mon Nov 07, 2011 4:10 am
Contact:

Re: IOS Standalone-error: "could not find a valid iden...[SO

Post by SusanB » Thu Jan 08, 2015 9:37 pm

SOLVED! I am now one happy and relieved LC developer :) I revoked the development certificate with the missing private key in XCode, and requested a new one. Voila! (What a welcome site that little pop up stating "the standalone was successfully created" was.)

I was afraid to do the revoking because there were so many warnings about it being irrevocable etc. So I printed out all the info on everything to do with certificates and profiles from the Apple Developer site so I could have the directions in hand as I followed the steps to do so.

The next thing I am going to do is EXPORT the Certificates and Profiles. Somehow I missed that in the past. I think when I updated to Yosemite, that is when the essential private key was deleted from my keychain. Who would have known? Now I am on my way to getting the IOS 8 fix my iPhone App desperately needs to the App Store.

Many thanks to the kind and helpful responders to my frustrated requests. You're the best!

stan
Posts: 10
Joined: Thu Jul 17, 2008 10:28 am

Re: IOS Standalone-error: "could not find a valid iden...[SO

Post by stan » Sat Feb 20, 2016 5:21 pm

As I've been pulling my hair out over this error for the last couple of weeks I thought I'd share the details of the solution that worked for me as it appears to be slightly different to others.

When I checked my keychain for certificates my personal developer certificate was showing that the issuing authority was not trusted...so that's an Apple Macbook, running Apple OS failing to trust Apple Computing inc as the certificate issuing authority... I have no idea why but setting the certificate to "manually" trust the issuing authority fixed the issue and I can now happily build apps again!!!

Post Reply