iOS standalone - what to do about code signing failures?

[Graham Samuel]

Wow! Breakthrough - thanks to you Dave and to Jacque. I deleted some 'old' certificates in the Keychain utility and suddenly the app got made. There is so much there that I didn't understand - as I've said before, I will try to get more of an insight and publish it. So far the lesson is "don't try to replace or renew, create new certificates and revoke or delete the old ones", and take no notice of the 'renew' button in the corner. Why for example are there are other certificates in the keychain which have expired but which never seem to prevent anything on my system happening? Why is there a keychain at all (Mac heresy!).

As to what you're seeing Dave, until a few minutes ago I wasT getting very much the same as you. There were two screens. For me the odd thing is that none of these great long numbers nor the shorter sequences were recognised as anything attached to my certificates as shown in the Finder nor to my App Identifier, unless I'm mistaken - what are they and where do they come from? I also think the two screens are the same, just one comes from within LC and another is some kind of by-product of LC's interaction with XCode.

Graham

On 6 Jan 2013, at 21:30, Dave Kilroy wrote:

> Hi Graham
> 
> If I try to build a standalone for iOS I'll get two error messages; the first alert (showing the LiveCode logo) says:
> 
> "Codesigning failed with 1) 0C076C94DC082497E47F5FA2F5A390A29E2C400 "iPhone Developer: Dave Kilroy (E7QB8D7WFM)" "
> 
> As well as a "1)" I'll also get a "2)" a "3)" and a "4)" failures, most but not all apparently lined to my 'bad' developer certificate
> 
> If I 'OK' that error message I'll get another, this time with a red 'X' symbol telling me that "There was an error saving the standalone application" with the same error from the previous alert repeated
> 
> What do you see when your codesigning fails? With any luck you don't have the same problem I have!
> 
> BTW, just in case you seem to have an extra, unwanted certificate, it is worth checking that KeyChain (watch out for storage of public and private keys) and Xcode (watch out for the Preferences folder in the Library) are not holding copies of such a certificate on your hard-drive
> 
> Good luck!
> 
> Dave
> 
> 
> 
>> I've been posting about certificate renewal etc so that I can go on with iOS development after my profiles / certificates or whatever have expired. I thought I had created a new set of stuff, and XCode now reports that I have valid Provisioning Profiles (don't know why I've got more than one, but I have), plus a (valid) specific profile on the device I'm currently trying to test on (an iPad 2).  Oh, and I also have active ad hoc distribution certificate.
>> 
>> My app works in the simulator, but when I try to save it as a standalone in order to get it onto the iPad, I get codesigning failures: there seem to be six failures (whatever that means) and two of these look identical. I did not get these when I first set up my (now expired) digital 'asset's (/rant don't you hate the hijacking of perfectly good English words for weird technical purposes? /rant).
>> 
>> Can anyone tell me how to track down these failures and correct them? I just have no idea how to start. I haven't found anything helpful in the iOS notes for LC either. The only clue I have is that the XCode organizer seems to think I'm two teams with slightly different names. I would gladly delete one of these if I knew how, and I suppose it might help.
>> 
>> I've been staring at the Apple documentation for most of the day but I am well and truly stuck.
>> 
>> Anxious
>> 
>> Graham
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode