Help! IOS Certificate not found on new MacBook?

Solar2D iOS
#1

Hello guys,

I am the proud owner of a Macbook Air and I am trying to setup my Corona SDK on it. So far so good but I am having problem with the certificate and how to setup the laptop for it. Until now I had my Mac Mini setup but I am not sure how to setup my new Macbook using the same certificate and provisionning profiles that I already on my Mac mini. Of course the goal is to to be able to dev and build while on the go with this beautiful new machine!

Here what I did so far in case anybody can see where I went wrong:

1- DL Corona SDK latest build

2- DL Code helper PRO

3- Exported the ad-hoc provisioning profile (from my Mac Mini( and then imported on my new macbook)

4- Went to App dev site and found my certificate on DL. Double click on it.

When I try to build my app, I can see the provisioning profile BUT it is grayed with the message:

“Certificate not install”

I am not sure how to “install” the certificate? Is this something I need to export from my Mac Mini to the new Mackbook OR this is something (certificate) I need to re-create from scratch like I did the first I setup the Mac mini couple a years ago?

I have to admit I am little (ok, a lot!) lost!

THANKS for any pointers.

Mo

#2

Mo, I think your Mac Air need to assume your Mac Mini’s identity.  To do so, you need to export your identity certificate from Mac Mini to your new Mac Air.  I don’t remember off the top of my head how to go about doing this properly, but… Ah, I just did a quick google search, and this came up:

http://stackoverflow.com/questions/7006845/the-issues-of-exporting-importing-certificate-private-key-under-keychain-acces

If the Stackoverflow response didn’t quite do it for you, look around for the answer, and I’m sure you’ll find it.

Good luck.

Naomi

#3

Thanks so much Naoimi. I will try that. Last night I was able to build an app on the MacBook by requesting a new certificate. Now I can see two certificates when I build (different dates) so I may not resolved the issue by doing that. Still I was able to build the app and uploaded to the device from the MacBook Air. Still I think I need to follow your suggestion and export my dev identity from the Mac mini to the MacBook. I really want to be able to build from both. Thanks again. Mo

#4

Hey, Mo, if you were able to build and install your app with MackBook Air without messing with keychain, maybe that’s all you need to do.  I think the identity is important for release builds, but if your new identity on MacBook Air doesn’t cause any problems with your existing app, then you might just not need to worry about it.  And I definitely wouldn’t worry about dev identity.

I haven’t read much about keychain and identity issue lately, so what I sort of remember could be outdated anyhow?

Naomi

#5

You have a point. I probably leave it as it is and use my old Mac mini for releasing apps to ITC and use he MacBook just for dev (ad-hoc) Thanks agin. Mo Ps: I hate this certificate, proviso ing business :slight_smile:

#6

Mo, I think your Mac Air need to assume your Mac Mini’s identity.  To do so, you need to export your identity certificate from Mac Mini to your new Mac Air.  I don’t remember off the top of my head how to go about doing this properly, but… Ah, I just did a quick google search, and this came up:

http://stackoverflow.com/questions/7006845/the-issues-of-exporting-importing-certificate-private-key-under-keychain-acces

If the Stackoverflow response didn’t quite do it for you, look around for the answer, and I’m sure you’ll find it.

Good luck.

Naomi

#7

Thanks so much Naoimi. I will try that. Last night I was able to build an app on the MacBook by requesting a new certificate. Now I can see two certificates when I build (different dates) so I may not resolved the issue by doing that. Still I was able to build the app and uploaded to the device from the MacBook Air. Still I think I need to follow your suggestion and export my dev identity from the Mac mini to the MacBook. I really want to be able to build from both. Thanks again. Mo

#8

Hey, Mo, if you were able to build and install your app with MackBook Air without messing with keychain, maybe that’s all you need to do.  I think the identity is important for release builds, but if your new identity on MacBook Air doesn’t cause any problems with your existing app, then you might just not need to worry about it.  And I definitely wouldn’t worry about dev identity.

I haven’t read much about keychain and identity issue lately, so what I sort of remember could be outdated anyhow?

Naomi

#9

You have a point. I probably leave it as it is and use my old Mac mini for releasing apps to ITC and use he MacBook just for dev (ad-hoc) Thanks agin. Mo Ps: I hate this certificate, proviso ing business :slight_smile:

#10

I think I have the same problem and I can’t find a solution…

I had to reinstall all my mcbookpro and then, I created a new certificate for development that worked pretty well.

The problem is that now I want to update my last app Neon Pong, and I need to install the certificates I used before I restarted my mcbookpro.

I saved a copy of the certificates, but also they’re in the iOS Certificates section in the member center. I downloaded the certificates and then installed them. 

In Xcode5 It seems to be all ok in preferences–>accounts --> view details (The signing identity and the profile is there)

I can see also the certificate in keychain access

But if I try to build in corona -->  I open the “Code Signing Identity” tab and --> (Certificate not installed) [neonpongdistribution]

I’ve been trying all the day and I can’t find a solution…

I’ll continue trying for days so, If I find the solution I’ll answer here again.

#11

Hi @pabloisidro,

Did you restart Corona after installing the new certificate(s)? You must restart after doing that, so Corona recognizes which certificates are currently installed.

Best regards,

Brent

#12

Thanks Brent, but that wasn’t the problem.

Well I didn’t understand well all the certificates with apple. With android is easy, you have a “key” file, and that is all, with that file you can build again new versions of your app.

I thought that with apple would be the same but, unfortunately, just saving the “Certificate” and the “profile”, I think you cant install correctly the certificates in a new mac, because you also need the “keys” of the keychain access. When I formated my mac, I only saved the certificates but I didn’t make a backup of all the keys system.

The only one solution for me was do again all the process again -> http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

Request a Certificate From a Certificate Authority etc. But creating a new Certificate

I’m not sure but I think I won’t be able to update my Neon Pong app on iOS… :frowning:

As an advice for the future -> Go to keychain access, export all the private and public keys of distribution profiles and save them (like in android)
 

#13

I think I have the same problem and I can’t find a solution…

I had to reinstall all my mcbookpro and then, I created a new certificate for development that worked pretty well.

The problem is that now I want to update my last app Neon Pong, and I need to install the certificates I used before I restarted my mcbookpro.

I saved a copy of the certificates, but also they’re in the iOS Certificates section in the member center. I downloaded the certificates and then installed them. 

In Xcode5 It seems to be all ok in preferences–>accounts --> view details (The signing identity and the profile is there)

I can see also the certificate in keychain access

But if I try to build in corona -->  I open the “Code Signing Identity” tab and --> (Certificate not installed) [neonpongdistribution]

I’ve been trying all the day and I can’t find a solution…

I’ll continue trying for days so, If I find the solution I’ll answer here again.

#14

Hi @pabloisidro,

Did you restart Corona after installing the new certificate(s)? You must restart after doing that, so Corona recognizes which certificates are currently installed.

Best regards,

Brent

#15

Thanks Brent, but that wasn’t the problem.

Well I didn’t understand well all the certificates with apple. With android is easy, you have a “key” file, and that is all, with that file you can build again new versions of your app.

I thought that with apple would be the same but, unfortunately, just saving the “Certificate” and the “profile”, I think you cant install correctly the certificates in a new mac, because you also need the “keys” of the keychain access. When I formated my mac, I only saved the certificates but I didn’t make a backup of all the keys system.

The only one solution for me was do again all the process again -> http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

Request a Certificate From a Certificate Authority etc. But creating a new Certificate

I’m not sure but I think I won’t be able to update my Neon Pong app on iOS… :frowning:

As an advice for the future -> Go to keychain access, export all the private and public keys of distribution profiles and save them (like in android)