Certificate not installed, can't build for IOS

Solar2D iOS
#81

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
#82

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.

#83

Thanks Tom. Isn’t it lovely when Apple break things? Shuts the door on everyone who might need to use legacy builds for whatever reason.

#84

I’ve the same problem. Waiting for the bug fix! +1

#85

I did the MacOs reinstallation… :frowning:

#86

Glad I found this. I thought there was an issue with my computer for a second.

Edit: Getting an error with the Info.plist now when I try to build (for development).

The error says “failed to load /tmp/lua_ohLl1F: 1” in terminal. This error does not come up with the latest public release. I’ve made sure there are no spaces in the project folder name.

#87

Also waiting for the update in the public release build because of this error, any update on this is greatly appreciated.  :slight_smile:

#88

I’m having a similar issue as naveen_pcs where I am getting this error when compiling:

Corona Simulator[14490]: Runtime error
    ?:0: attempt to index a nil value
stack traceback:
    [C]: ?
    ?: in function ‘modifyPlist’
    ?: in function ‘?’
    ?: in function <?:628>

I have filed a ticket.  I’m unable to release an app as a result of this block since I’m using an updated cert.  :frowning:
 

#89

We just updated a fixed 2393 build that fixes the iOS Profile/Cert problem. We are calling this 2014.2393a and it only affects the Mac Simulator. You can download it at our public download page: https://developer.coronalabs.com/downloads/coronasdk

There is an issue with Daily Build 2398 and we don’t recommend using that build because of a build error causes by spaces in the file name path.

Lets us know if you’re seeing certificate problems caused by THIS release.

Thanks,

Tom

#90

Thank you, it seems to be working now, choosing the previously grayed-out code identity that is. :wink:

#91

Tom:

GREAT NEWS!  Not only does 2398a fix the cert issue, but the compiling error I was getting with 2398 has disappeared!  (I don’t have the ticket number associated with the report I filed today but you can probably close that now.)

I am uploading our test build to TestFlight as I write this.

Thanks SO much for not letting this issue twist in the wind.

Now, thinking ahead… this profile issue is going to cause some headaches for developers using older reference SDKs to release apps to older targets.  Ugh.

#92

Build 2393a fixed this problem for me.

I’m glad I found this thread. I was building on a new Mac for the first time and thought it was somehow related to that. Good work dev team!

#93

It worked at first, but as I encountered the issue that the Application Loader was rejecting my app with:
"ERROR ITMS-9000: “Missing or invalid signature… app is not signed using an Apple submission certificate”.

I decided to follow the advice in other topics to remove all old provision profiles and keychain certificates. So I did, started fresh and remade them all in the iOS app developer interface.

This time however it now says (again) when I want to build the app with Corona: “Certificate not installed” and my new code signing identify is grayed out just like prior to 2393a which you just released.

Any ideas? Anyone else still experiencing problems with this?
I was quite sure things would work from here on and out, especially since I did everything anew without old certificates and profiles possibly interacting with things… :confused:

Are there any other possible reasons as to why my new code signing identity would be now suddenly grayed out?
Thank you for any advice.

Ps

  • Ive tried reinstalling the 2393a corona version, it did not help.
  • Ive also tried re-adding the older provision file identity into my library (the one that was grayed out but started working again after installation of 2393a, it is now also grayed out.

____________
SOLVED: I had simply missed that I should download the certificate once created and insert it into my keychain. If you miss this action then the provision identity might be visible in corona but grayed out. Just saying it to you others who might do the same “Blunder”. :slight_smile: *coughs*

#94

Glad you resolve the problem with the missing certificate.

The provision file identify will be grayed out in Corona if there is no Certificate (developer or distribution) installed in your keychain. It’s also possible to have a distribution certificate and do a build but have it rejected by the Application Loader if the provision file is NOT linked to the installed certificate. It took me an hour to figure this out and resolve the problem while testing the 2393a build.

#95

@tschussler, Apple changed the requirement that apps be built with Xcode 5.1.1 a few months ago.  No one using public builds older than 2189a can submit to Apple anyway (that’s why we have an “a” version  of that public build).  Since there are no significant differences (i.e. Graphics 1 vs. Graphics 2) between 2393a and 2189a, (well there are physics changes that impact really small physics objects), this shouldn’t be much of an issue.

The only places you can submit pre-2189 apps to is Barnes & Noble and Amazon.

Rob

#96

Hi
Is there any public release fixing this issue?

#97

It’s not a new public release, but a patched version of 2393 called 2393a.  If you download the Mac version from the main download page you should get the new version.

Rob

#98

Public release 2393 works perfect. Problem solved for me too.

Thank you for quick response.

#99

this bug made me suffer a while, thanks for the fix

#100

the new release fixed the problem here, thanks for the quick action team Corona!