Choose from the following - (Certificate not installed) when trying to build from Corona

Getting Started Newbie Questions
#1

Hello,

I’ve seen other people with this same issue, but even after reading their solutions I’ve been unable to get my project to build. It all started today by magic. All of a sudden, when trying to build the app, Corona doesn’t allow me to select my code signing identity. Instead, it shows:

Ug. So, I decided to wipe out everything and start from scratch. But it still didn’t work! Here’s exactly what I did.

First, I wiped out everything related to provisioning that I know how to. Here’s my Keychain Access manager after having cleaned everything out:

And here’s my Provisioning Profiles screen in XCODE:

I also made sure that all files were cleared out of /Users/(your user)/Library/MobileDevice/Provisioning Profiles/. At this point, when I try to build in Corona, nothing is listed under “Code Signing Identity”:

Looks pretty clean. So, next I start following Corona’s build tutorial (http://developer.coronalabs.com/demo/DeviceBuildGuide.pdf). First step: Request a Certificate from a Certificate Authority:



Everything went fine. Next, time to get my new Development Certificate:




Which I download…

… and double click on. When I double click on it, the Keychain Access screen opens and I do see some new stuff in there:

I’m assuming this is all correct. My device is already added to my Apple Development account, and I already have an App ID. My app’s name recently changed, but I was pretty sure that I successfully built with the new name. I only changed the name in Corona. I didn’t modify the App ID or anything strange.

I now create both a Development and Distribution profile.


As you can see, an old Invalid provisioning profile existed called “BT Dev Prov Prof”. Once I created my new profile, I was able to remove the old Invalid profile

And I did the same for the distribution profile:

I downloaded the distribution profile and copied it to /Users/(your user)/Library/MobileDevice/Provisioning Profiles/

And finally, attempted to build again in Corona:

Curse you, Apple!!

Can anyone help me out?

Thanks,

  • Bret
    [import]uid: 168791 topic_id: 31925 reply_id: 331925[/import]
#2

Ah, I think I accidentally de-authorized my version of Corona. It’s tricky, because when I’m using macincloud, the Corona welcome screen is just a big black rectangle. I’ll follow up when I find out for sure.

EDIT: Nope, that’s not the problem. Back to the drawing board… [import]uid: 168791 topic_id: 31925 reply_id: 127371[/import]

#3

I’ve tried one more thing which didn’t make any difference, but I wanted to share. I added Apple’s root certificates to my keychain:

It’s worth noting, too, that my provisioning profile when viewed in XCODE says, “Valid Signing identity not found”:

Thanks for any help. I’m really stuck.

  • Bret [import]uid: 168791 topic_id: 31925 reply_id: 127372[/import]
#4

I think one problem might be that my private keys are not installed, but I can’t figure out for the life of me why. (see http://stackoverflow.com/questions/11607547/valid-signing-identity-not-found-on-new-computer)

Again, any advice would be awesome. I’ve been working on this for probably 12 hours by now. GAK. [import]uid: 168791 topic_id: 31925 reply_id: 127374[/import]

#5

Ok, I tried another way… and still failure. But maybe it might be helpful for the kind people over at Corona to help me troubleshoot my issues. Basically, I tried letting XCode do all of the work for me by clicking on Refresh on the Devices tab. Here were my steps:

First, I cleared everything out of XCode, The Keychain Access, and revoked my development and distribution certificates from the Apple developer portal:

Then I click Refresh in XCode’s Provisioning Profiles and was prompted to enter my login info:

XCode then told me I had no iOS Development Certificate or iOS Distribution certificate. I asked it both times to request one on my behalf:


Once it was finished, it showed me the developer provisioning profile, but it still said that “Valid signing identity not found”.

But in the keychan access tool, things looked better:

So, I decided to try building my app…and (drum roll please)…

FAILURE!!

I hope this extra information might help someone spot my issues.

Thanks,

  • Bret
    [import]uid: 168791 topic_id: 31925 reply_id: 127396[/import]
#6

Ah, I think I accidentally de-authorized my version of Corona. It’s tricky, because when I’m using macincloud, the Corona welcome screen is just a big black rectangle. I’ll follow up when I find out for sure.

EDIT: Nope, that’s not the problem. Back to the drawing board… [import]uid: 168791 topic_id: 31925 reply_id: 127371[/import]

#7

I’ve tried one more thing which didn’t make any difference, but I wanted to share. I added Apple’s root certificates to my keychain:

It’s worth noting, too, that my provisioning profile when viewed in XCODE says, “Valid Signing identity not found”:

Thanks for any help. I’m really stuck.

  • Bret [import]uid: 168791 topic_id: 31925 reply_id: 127372[/import]
#8

I think one problem might be that my private keys are not installed, but I can’t figure out for the life of me why. (see http://stackoverflow.com/questions/11607547/valid-signing-identity-not-found-on-new-computer)

Again, any advice would be awesome. I’ve been working on this for probably 12 hours by now. GAK. [import]uid: 168791 topic_id: 31925 reply_id: 127374[/import]

#9

Ok, I tried another way… and still failure. But maybe it might be helpful for the kind people over at Corona to help me troubleshoot my issues. Basically, I tried letting XCode do all of the work for me by clicking on Refresh on the Devices tab. Here were my steps:

First, I cleared everything out of XCode, The Keychain Access, and revoked my development and distribution certificates from the Apple developer portal:

Then I click Refresh in XCode’s Provisioning Profiles and was prompted to enter my login info:

XCode then told me I had no iOS Development Certificate or iOS Distribution certificate. I asked it both times to request one on my behalf:


Once it was finished, it showed me the developer provisioning profile, but it still said that “Valid signing identity not found”.

But in the keychan access tool, things looked better:

So, I decided to try building my app…and (drum roll please)…

FAILURE!!

I hope this extra information might help someone spot my issues.

Thanks,

  • Bret
    [import]uid: 168791 topic_id: 31925 reply_id: 127396[/import]
#10

Wow, that’s a lot of screenshots.

OK, so, I’m not sure if you’ve been through the walkthrough threads in Device Builds Support sub forum or not but they are worth a look. This is a long thread obviously and quite a lot to look over - I’d encourage you to review the mentioned threads and then, if still having problems, email me again and will see what we can do. [import]uid: 52491 topic_id: 31925 reply_id: 127724[/import]

#11

I’m having the EXACT problem! I’ve posted on the forums numerous times and either got no response or just “check your key chains”.

I also contacted and did a walk through with Apple Support. They said everything is fine with my keychain and certificates are valid. Yet I constantly get this error. I’ve cleared my keychain, deleted profiles, certificates MANY times and did the walk through countless times. I even did a whole reinstall of my os x and STILL it’s not working. I’m not a happy camper. [import]uid: 114389 topic_id: 31925 reply_id: 127762[/import]

#12

Hey Silky, certificates and provisioning profiles can be incredibly frustrating - I know. To confirm your certificates are fine can you please build a sample Xcode project using the same cert and profile that you are attempting to build with Corona and let me know how you go? [import]uid: 52491 topic_id: 31925 reply_id: 127844[/import]

#13

I re-installed my whole OS X, re-did my certs and profiles and it wouldn’t build on Corona. But I did as you said and built for X-Code successfully, and now it’s magically working in Corona! I don’t know if that’s required, but it worked for me :smiley: [import]uid: 114389 topic_id: 31925 reply_id: 127859[/import]

#14

Wow, that’s a lot of screenshots.

OK, so, I’m not sure if you’ve been through the walkthrough threads in Device Builds Support sub forum or not but they are worth a look. This is a long thread obviously and quite a lot to look over - I’d encourage you to review the mentioned threads and then, if still having problems, email me again and will see what we can do. [import]uid: 52491 topic_id: 31925 reply_id: 127724[/import]

#15

I’m having the EXACT problem! I’ve posted on the forums numerous times and either got no response or just “check your key chains”.

I also contacted and did a walk through with Apple Support. They said everything is fine with my keychain and certificates are valid. Yet I constantly get this error. I’ve cleared my keychain, deleted profiles, certificates MANY times and did the walk through countless times. I even did a whole reinstall of my os x and STILL it’s not working. I’m not a happy camper. [import]uid: 114389 topic_id: 31925 reply_id: 127762[/import]

#16

Hey Silky, certificates and provisioning profiles can be incredibly frustrating - I know. To confirm your certificates are fine can you please build a sample Xcode project using the same cert and profile that you are attempting to build with Corona and let me know how you go? [import]uid: 52491 topic_id: 31925 reply_id: 127844[/import]

#17

I re-installed my whole OS X, re-did my certs and profiles and it wouldn’t build on Corona. But I did as you said and built for X-Code successfully, and now it’s magically working in Corona! I don’t know if that’s required, but it worked for me :smiley: [import]uid: 114389 topic_id: 31925 reply_id: 127859[/import]

#18

My certificate expired today, and I’m having no luck at all getting it renewed properly. @Bret, were you able to fix your problem? I do not want to re-install my whole OSX to get my system to start generating AdHoc and Release builds properly.

I mean, it was quick enough to get the certificates renewed, but for life of me, I am absolutely unable to generate builds without code-signing error message. @Bret, I’ve cleared out my keychain and went through pretty much the same steps you’ve gone through, but I’m having no luck at all. How extremely frustrating.

Naomi

UPDATE: My issue is finally solved. The problem with mine was, somehow, my keychain access.app was completely messed up, and eventually it stopped generating private/public keys. I mean, it simply did not generate any keys at all. I scoured the web and tried everything (thinking I’ve got nothing to lose at that point.) Then I stumbled across this thread:

http://hints.macworld.com/article.php?story=20060318124936642

I tried [text]sudo mv /Library/Keychains/System.keychain /Library/Keychains/System.keychain.bak[/text] and [text]sudo /usr/sbin/systemkeychain -C[/text], but I don’t think it really helped. But then… I run these commands: [text]sudo systemkeychain -vfcC[/text] and [text]systemkeychain -vt[/text]. And then I also run disk utility app, repairing permissions, etc., etc., etc.

I don’t even remember what else I did (but I know I did lots more.) Anyhow, somehow, eventually, my keychain access app got normalized, and it was able to generate private/public keys. Once it did that, everything else fell into place properly, and worked like a charm.

Well, one good thing that came out of this struggle was that I finally got my dev certificate working too. Now I can generate builds using dev certificate as well as adhoc and standard distribution certificates without getting code-signing errors.

EDIT : One thing I should remember (and I’m editing this just in case I face the very same problem next year and need to jog some memory) is that, I got Developer Certificate working via Xcode, doing Refresh (although I don’t remember what steps I took before I hit Refresh). However, I could not get valid Distribution certificates that way. So I went through the usual, requesting CertificateSigningRequest using certificate assistant and submitting the CSR via Apple Developer site, downloading it and then double clicking on it – which finally added the valid certificate for a valid public/private key pair.

But, still… Ugh. Why does Apple make us go through this wringer every year?

Naomi [import]uid: 67217 topic_id: 31925 reply_id: 134464[/import]

#19

My certificate expired today, and I’m having no luck at all getting it renewed properly. @Bret, were you able to fix your problem? I do not want to re-install my whole OSX to get my system to start generating AdHoc and Release builds properly.

I mean, it was quick enough to get the certificates renewed, but for life of me, I am absolutely unable to generate builds without code-signing error message. @Bret, I’ve cleared out my keychain and went through pretty much the same steps you’ve gone through, but I’m having no luck at all. How extremely frustrating.

Naomi

UPDATE: My issue is finally solved. The problem with mine was, somehow, my keychain access.app was completely messed up, and eventually it stopped generating private/public keys. I mean, it simply did not generate any keys at all. I scoured the web and tried everything (thinking I’ve got nothing to lose at that point.) Then I stumbled across this thread:

http://hints.macworld.com/article.php?story=20060318124936642

I tried [text]sudo mv /Library/Keychains/System.keychain /Library/Keychains/System.keychain.bak[/text] and [text]sudo /usr/sbin/systemkeychain -C[/text], but I don’t think it really helped. But then… I run these commands: [text]sudo systemkeychain -vfcC[/text] and [text]systemkeychain -vt[/text]. And then I also run disk utility app, repairing permissions, etc., etc., etc.

I don’t even remember what else I did (but I know I did lots more.) Anyhow, somehow, eventually, my keychain access app got normalized, and it was able to generate private/public keys. Once it did that, everything else fell into place properly, and worked like a charm.

Well, one good thing that came out of this struggle was that I finally got my dev certificate working too. Now I can generate builds using dev certificate as well as adhoc and standard distribution certificates without getting code-signing errors.

EDIT : One thing I should remember (and I’m editing this just in case I face the very same problem next year and need to jog some memory) is that, I got Developer Certificate working via Xcode, doing Refresh (although I don’t remember what steps I took before I hit Refresh). However, I could not get valid Distribution certificates that way. So I went through the usual, requesting CertificateSigningRequest using certificate assistant and submitting the CSR via Apple Developer site, downloading it and then double clicking on it – which finally added the valid certificate for a valid public/private key pair.

But, still… Ugh. Why does Apple make us go through this wringer every year?

Naomi [import]uid: 67217 topic_id: 31925 reply_id: 134464[/import]

#20

I am having the same issue. The distribution certificate is NOT installed. I followed the .pdf file as well.

When I double click the distribution certificate, the “login” menu does NOT appear.

Corona can you try to do this?

I am unable to associate the distribution certificate with my private “Team Leader” key. [import]uid: 198389 topic_id: 31925 reply_id: 136688[/import]