Can't figure out 'No Code Signature'

[bdtrauma]

After trying multiple times to get rid of the 'No Code Signature' error in Xcode when I drag my Livecode app into the organizer I am exhausted. I cannot get this error to go away. I've gone through multiple tries at creating new certificates, provisioning profiles etc... and I still get that error.

I'm using Livecode 4.6.4 and Xcode 4.1 Build 48110f...

Any way to get around this or fix it? I've asked the question before but no solution yet.

Bert

[Randy Hengst]

I had the same problem. The only way I fixed it was to open my stack in 4.6.1.... I was then prompted to confirm access to the signature. 4.6.1 then worked as did 4.6.4.

be well,
randy hengst

[CALL-151]

I haven't had this problem since 4.6.2, but when I did AppResigner fixed it.

http://www.gorbster.net/blog/archives/273

[Jellicle]

I had this happening for about 6 weeks recently. In the end I rebuilt my entire development environment, including all my certificates (following the Apple guide, step by bloody step), provisioning profiles, installing xCode, LiveCode...everything. And it worked. But it was a total pain.

Gerry

[bdtrauma]

Thanks... I used the appresigner and it found that I had two conflicting certificates. Once I deleted one of them in keychain and resigned using appresigner it worked!

Thanks,

Bert

[FireWorx]

I cant say enough about that little ApResigner program. I was at logger heads trying to get my standalone onto my Ipad test devise. Just go to your keychain access folder and double click on your Iphone Developer Your Name (44h5534h43) Id and hit copy. Then launch the ApResigner Icon, paste your Id in the box when promted. Apresigner gives you a favorable message. Then drag and drop the standalone icon that just got "blessed" over the Ipad devise icon that is hooked up by cable to your Mac. Walla! Your ap is now on your Ipad! Love it when things work!
Dave

[PaoloMazza]

Hi all,
I had the same problem moving my app to the iPhone today. First I had to renew my provisionig profile, then I realized that I had two different certificates installed (the expired one and the new one) that were similar in the Key Chain. Probably LiveCode was getting confused even though I had the correct provisioning profile selected in the build settings. I opened Keychain Access and manually deleted the old certificate. Now it works.
All the best. Paolo Mazza