Certificate Not Installed Problem When Build For Device

Solar2D Monetization (in-app purchases, ads, etc.)
#21

Daniella, please update to 2401.

Rob

#22

I have been pulling hair all day trying to get the grayed out code signing identity to work.  Everything was checked green in the Xcode organizer window and everything appeared okay in the keychain.   

I upgraded to build 2401 and everything works!!!    Glad I found Robs post - Thanks!

Been waiting to get things up in iOS before making the announcement - things are going well in the Google Play Store - J-

#23

Also having this issue. Will 2401 be available to the general public soon?

#24

What version of Corona SDK are you using?  There is a 2393 and a 2393a for Mac users.  The 2393a version does not have this issue.  Make sure you’re running that version.

#25

Thanks, 2393a fixed the issue - I was running 2393.

#26

Hi Rob,

My code is in graphics 1.0 so i am using build 1202 for this.
Now, i want to install profile(For ios build) but i am getting error “certificate not installed”.

So how can i create build in graphics 1.0?

Any updated build for graphics 1.0 with solved this issue?

Thanks.

#27

You cannot submit a 1202 built app to iOS any longer.  You have not been able to for some time due to breaking changes Apple has made.  We cannot update the Graphics 1.0 line.  If you want to submit to Apple, you must use public build 2393a or daily build 2401 or later.  That said, we are getting reports that Apple made another change today which make make even those builds have problems.  We are investigating…

In your case, since you are an Enterprise subscriber, you should be able to build your app from Xcode which would manage your profiles correctly (though you have to use Xcode 5.1.1 or later). 

So if you wish to use Corona SDK to build your apps you must update.  You should be able to get mostly there by adding:

graphicsCompatibility = 1

to your config.lua where you set the width and height.  If you are dependent on the legacy sprite library you can download it from Github and just drop the sprite.lua in with your main.lua.  Almost everyone who has done this has only had to make a few minor updates to get their app running under Graphics 2.0.

It is very impractical to try and maintain older builds of a product and in the environment where our upstream hosts like Apple and Google make changes, we have to react to them and that happens in the latest daily and public builds.

Rob

#28

Hi @RobMiracle - can I confirm that this now makes us unable to build on *any* graphics 1.0 version of Corona SDK if we’ve updated our certificates recently?

I have a massive problem with graphics 1.0 not running correctly (even with compatibility = 1) as per http://forums.coronalabs.com/topic/47664-issues-with-graphicscompatibility-1/.

Is this now a drop-dead for graphics 1.0?

Thanks,

Nathan.

#29

This has now become time critical for me - can you please let me know one way or another @RobMiracle?

Thanks,

Nathan.

#30

I don’t know how I can make this more clear.

You cannot build for Apple iOS without using the latest public build (2393a) or daily build 2424 or later.  And as of right now you can’t event submit with those builds because Apple is still making changes to their submission process.  It is absolutely impossible to use any older versions for iOS.  Once the submission process settles down and we address any thing else they are going to break, we will put out a new daily build that fixes this and then put out a new public build shortly afterwards that addresses it for the Starter and Basic subscribers.  Since all builds of Graphics 1.0 are older than 2393a, the cannot be used with Apple.

For Android, Google has changed the rules for using Advertising Identifiers.  This impacts AdMob and any Ad service using Google Play.  Also there may be core changes that we made around this.  As such, I would not trust using any build older than 2393 for submitting to Google.

Samsung requires their SDK’s to be included.  You cannot use any Corona SDK build to submit to Samsung.

This leaves Amazon, Barnes & Noble and smaller random Android stores as the only place you can publish Graphics 1.0 builds too.

Any new provisioning profiles created in the past few weeks absolutely will not work with Graphics 1.0 builds  or any build prior to 2393a (public) and 2407 (daily, though other Apple changes are forcing the use of 2424 or later).

Rob

#31

Thanks @RobMiracle - crystal clear. Time to port!!!

#32

I installed the most recent public build of Corona last week (mac), but have since renewed my distribution certificate as they had expired. All certificates are valid and listed as such in xCode, but now in Corona I’m no longer able to select my distribution code signing identity when I go to build for iOS. It says ‘(Certificate not installed)…’ I threw out Corona and reinstalled it but on launch it still listed my recent projects so thinking it’s cached my old certificates, or trying to link to files that no longer exist? Is that possible? 

Any suggestions would be appreciated.

Pete

#33

Hi Pete,

Can you do a full removal of Corona and then re-install? That includes going to:

[~] > Library > Application Support

And then removing both the “Corona Simulator” and “Corona” folders.

After that, trash the Corona SDK application folder and re-install. That should remove all history of the previous install.

Best regards,

Brent

#34

so said…

#35

Brent

I do that and it still knows my recent projects. Where else could it be storing this info? How can we get a truly clean reinstall?

#36

I also have created some new provisioning profiles (Apple Developer Center) and when trying to build with daily build 2014.2392 I can’t select the profiles from the list because they are listed in grey with the info “Certificate not installed”. But I didn’t do any changes on the Certificates, profiles etc.

Any ideas, what can cause this and how to solve the problem?

Daniela

#37

Hi Daniela,

This issue was caused by an Apple change and we fixed it in build 2393a (be sure and get the “a” one from the download page). Please download that build and things should work as expected.

Brent

#38

Daniella, please update to 2401.

Rob

#39

I have been pulling hair all day trying to get the grayed out code signing identity to work.  Everything was checked green in the Xcode organizer window and everything appeared okay in the keychain.   

I upgraded to build 2401 and everything works!!!    Glad I found Robs post - Thanks!

Been waiting to get things up in iOS before making the announcement - things are going well in the Google Play Store - J-

#40

Also having this issue. Will 2401 be available to the general public soon?