Certificate not installed, can't build for IOS

Solar2D iOS
#1

Hey,

When trying to build for IOS I can’t select the correct Code Signing Identity from the build menu, it’s been grayed out with a ‘Certificate not installed’ error.

I have read through this similar thread: http://forums.coronalabs.com/topic/33711-certificate-not-installed-problem-when-build-for-device/

and this doc: http://docs.coronalabs.com/guide/distribution/iOSBuild/index.html

…to no avail

What is odd is I have used different singing identities before for other apps, as you can see from the screenshot, these still work. There is only one iPhone dev and one distribution certificate linked to my account, and both are still there untouched in Keychain.

Any ideas?

Thanks!

wim

#2

I’m korean. sorry, i am poor english…

I have the same problem.

this is console log…

2014-08-12 19:06:58.160 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.161 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.161 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.162 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.162 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.163 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.163 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.163 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.164 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

2014-08-12 19:06:58.164 Corona Simulator[2038:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)

and screen shot.

rRoE9gr.png

The same thing with him, and I tried clean up all certificate, all keychain.
 

and, manually renew certificate, automatic renew certificate… (xCode -> preference -> account)

but, stiil didn’t work.

xcode build is work fine… 

but not only corona build…

How can I fix this issue? Any ideas?

#3

We have the exact same problem as mentioned. Profiles are greyed out and console write WARNING: Could not find certificate for identity ((null)) whose user id is: (null).

#4

Hi!

We have the exact same issue.

We have successfully used many Development and Distribution profiles for multiple apps in the past, the last time being 3 weeks ago. Some of the profiles have started expiring so we are replacing them. But after reinstalling them they appear grayed-out in Corona’s build dialog, with a message “Certificate not installed”. The last replacing 3 weeks ago didn’t have such problems.

The console log is as Choi Hyun Seok said.

The profiles from 3 weeks ago still seem to work, but any re-issued ones are consistently rejected.

We tried this with both Development and Distribution profiles with the same results.

We tried on two different machines, managed by 2 people with their own dev certificates, etc - still the same thing.

All the necessary developer certificates AND the relevant private keys are installed on both machines - so this is not the problem for sure. Especially given that we did successful builds several weeks ago.

We tried Corona builds 2381 and 2393.

We are on Mac OS X 10.9.4. I don’t know if this is related, but our machines have recently underwent a security update as described here:

http://support.apple.com/kb/HT6296

which has changed the trusted certificates authorities as described here:

http://support.apple.com/kb/HT6005

As this looked like a caching issue with old expired profiles, we also tried force-uninstalling Corona along with its files in /Library/Preferences and /Library/Application Support. This turned out to be a VERY BAD idea, as now the computer is locked out of Corona, without the ability to log in with its own license.

Does anyone have any other insights?

#5

The same thing happens to me.

The old profile worked well, but i’ve deleted it. After that I’ve installed new ones and all of them are greyed out.

What i’ve tried to:

  • Delete Corona (including Application Support/Corona* folders), update Corona to the newest version (2393)

  • Delete all certificated and keys from this computer

  • Revoke certificates from apple developer and create new ones, create new app id, create new Profiles

  • Delete profiles in Library/Mobile Data/ and copy newly created to this folder.

  • Use old corona version (worked today with old profile, 2381)

Nothing works… Xcode show green lights, so I suppose, xcode works well, but not Corona

#6

+1 Just tried to set up push notifications today and I am having the same problem! I have successfully installed certificates, provisioning profiles etc countless times!

#7

+1

Glad I found this thread, although not before I’d cleared all my certificates and provisioning profiles out and started again twice.

I created some new provisioning profiles today and those came up ‘certificate not installed’ in Corona, even though other profiles generated yesterday from the same certificate were fine. 

What’s going on??

#8

Has anyone submitted a bug report on this? should we?

#9

I’ve tweeted Rob Miracle to draw his attention to it - but we can’t be sure if this is a Corona issue or Apple.

Have any of you got something you can build for native xCode to see if the profiles work that way?

#10

Same issue here, I made a provision a day later and keep getting certificate not installed, started over (deleted everything, made them again) and same problem. Someone should report this idk how

#11

I have exact the same issue.

#12

Hi guys,

Let me check into this and see what I can find out… I’ll report back as soon as I know anything new.

Brent

#13

Thanks everyone. We can duplicate the issue and looking into the solution now. Seems like Apple has changed something in the  Provisioning Profile.

#14

Any news

#15

Engineering has identified the problem and is working on a fix. 

Rob

#16

Yay!

#17

Yaaa! Same here! Glad to know Corona its fixing!

#18

Corona has a daily build that fix this issue, but comes another issue:

If I have localization file (pt-BR.lproj/infoPlist.strings), it wont compile.

If I remove the localization file, it compiles. But when I installing to device from xcode organizer, I got this:
The Info.plist for application at /Users/facv01/MyApp.app specifies a CFBundleExecutable of template, which does not exist

#19

We pushed daily build 2398 that fixes the Apple Provisioning Profile/Cert issue. We made a few other changes in the build and it introduces an error for projects that contain spaces in the project folder/name. So if you build a project like “Hello World”, it will fail. If you remove the space it works. We will try to correct it ASAP.

We are working on patching our Release Build to fix the Provisioning Profile/Cert issue. We hope to have that available in the next day or two. I’ll update this thread when a new public release is available.

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

thank you for information. i also removed all certificates, reset keychain, reinstalled corona etc…

i was almost thinking to reinstall MacOs this morning. Today, this topic is a big relief for me.

now i am waiting for a public release.