iOS standalone - what to do about code signing failures?

Roger Guay irog at
Sun Jan 6 22:17:40 EST 2013

Ok, time for me to chime in.

I have:
Deleted all expired certificates from my Keychain. 
Deleted all Development and Distribution Provisioning Profiles for the team that I'm working on
and downloaded and installed fresh Provisioning Profiles from the Portal

And still my Xcode Organizer shows a status of "Valid signing identity not found" for the subject distribution profiles. (There is no indication of problems on the Portal i.e. status shows "Active")

Can anyone suggest anything else . . . pretty please?


On Jan 6, 2013, at 2:11 PM, J. Landman Gay <jacque at> wrote:

> First off, don't feel bad, I don't think anyone really gets what is going on. I just did whatever the site said to do and somehow it mysteriously worked. I haven't had to deal with expired certificates yet but I will within the next few weeks.
> From what I've heard on the list here, expired certificates can cause codesigning problems even if you have new ones. You have to make sure all the old ones are deleted. You can do that in XCode or directly in Finder. Some people just delete them all and then re-download and install the new ones.
> Once you've done that, you have reset the profile in LiveCode, even if it appears to be using one with the same name. It needs to be re-linked.
> The reason you have two certificates is because one is for you and one is for your "team". I generally use the team one. I don't know why.
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list