After a recent upgrade to a commercial license of LiveCode 5.5.3, I have just installed Mac OS X 10.8.2 and XTools 4.5.2 on a MacBook Pro (15" display, mid 2009).
LiveCode and the iOS simulator (version 6.0) are working fine.
However when trying to build a standalone app for iPhone, I get the following new error message:
QUOTE
There was an error while saving the standalone application
codesigning failed with 1) ECEF5…..5A05 "iPhone Distribution: myName"
2) 7C64A….7E92 "iPhone Developer: myName (MU…..G6)" [<- sequence of 10 letters and numbers]
UNQUOTE
Some time ago (several months ago) I could build a standalone without any problem, but it was not under the same LC version nor the same Mac OS version...
I have checked my certificates in Keychain Access, where I found 3 certificates:
- one valid "iPhone Distribution" under my name, valid until 8 Feb 2013.
- 2 "iPhone Developer" under the same name (and also the same sequence of letters and numbers between brackets after my name). One is still valid until Oct 2013, and one has expired in june 2012.
I'm really confused about the use of these certificates, and I'm not sure about what to do with the expired certificate. Keep it or delete it ?
Could anyone give me some advice on:
1) how to treat an expired certificate
2) how to renew a certificate due to expire soon
3) how to be able to build again a standalone app ?
Thanks.
Codesigning failure
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Codesigning failure
This just came up on the mailing list, the thread may help:
http://runtime-revolution.278305.n4.nab ... 58701.html
The short version is:
Remove all old certificates from Keychain.
Create new certificates (and provisioning profiles if needed) in the developer portal and install them.
Reset LiveCode's link to the profile in standalone settings.
http://runtime-revolution.278305.n4.nab ... 58701.html
The short version is:
Remove all old certificates from Keychain.
Create new certificates (and provisioning profiles if needed) in the developer portal and install them.
Reset LiveCode's link to the profile in standalone settings.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
GoneToSail
- Posts: 49
- Joined: Sun Jan 24, 2010 10:34 pm
Re: Codesigning failure
Many thanks Jacqueline !
You, and also the thread, of course, helped me very much.
I was more lucky than others as I just removed the expired certificate (which I did not dare to do so far) and I reset LiveCode's link… "et hop !" —as we say in french—, my piece of software came to life on my iPhone…
Great evening !
I fully agree with Graham Samuel-4 about the need for a document explaining Apple's process of certification which would be oriented towards LiveCode users, and if a draft comes out in the future, I would try to contribute to a french translation (as far as I would understand the original text…).
Again, thanks very much !
You, and also the thread, of course, helped me very much.
I was more lucky than others as I just removed the expired certificate (which I did not dare to do so far) and I reset LiveCode's link… "et hop !" —as we say in french—, my piece of software came to life on my iPhone…
Great evening !
I fully agree with Graham Samuel-4 about the need for a document explaining Apple's process of certification which would be oriented towards LiveCode users, and if a draft comes out in the future, I would try to contribute to a french translation (as far as I would understand the original text…).
Again, thanks very much !
Re: Codesigning failure
Thank you guys, after read the page linked by Jacque, I resolved a similar problem deleting all expired certificates from my Keychain.