You make a very good point Rob, thank you. I was forgetting that there was a 2189a build of the SDK.
For users getting build errors when using 2398 and 2399, please use 2401 instead. There was an issue causing a “plist” build error with the previous builds. We backed out the failing code in build 2401.
Please let me know how can fix it.
2014-08-15 11:07:29.905 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.906 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.907 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.907 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.908 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.908 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.909 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.909 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.910 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.910 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
2014-08-15 11:07:29.910 Corona Simulator[514:507] WARNING: Could not find certificate for identity ((null)) whose user id is: (null)
logout
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.
but Not corona build…
2393a install yes i solved it
This is exactly what I am experiencing!! I thought it had something to do with the fact that I created a new apple dev account for a group, and transferred it over. And after re-creating the certificates, it did not work. “Certificate Not Installed” is what I see on an unclickable option for my prov profile.
Has anyone found a way around this? I need to release a new version, and this has backed me up several days 
And I don’t have access to the daily builds because my paid membership ran out recently.
-----EDIT
I JUST FINISHED READING THE REST OF THE THREAD
This legitametely saved my life. I am so grateful!!! Thank you Corona!!!
If you’re experiencing this problem, please download the newly updated 2393a Mac Simulator build at our Public Download page. You don’t need to be a paid subscriber for this update. https://developer.coronalabs.com/downloads/coronasdk
Hello,
Am I the only one to still get the plist error?
Tried builds 2398, 2399, 2393a, and 2401.
None of them seem to have solved it for me (see screenshot).
I am positive I am using build 2401.
Here is my console output:
Created XCENT: /var/folders/11/bmcm_ld13zjc6gnvlgj7kfpw0000gn/T/CLtmpSiBSwy/entitlements.xcent
Creating Info.plist…
Usage: plistutil -i|–infile in_file.plist -o|–outfile out_file.plist [–debug]
-i or --infile: The file to read in.
-o or --outfile: The file to convert to.
-d, -v or --debug: Provide extended debug information.
Error: failed to load /tmp/lua_xB5s6N: 1
JSON:
2014-08-19 13:08:52.274 Corona Simulator[1432:507] Runtime error
?:0: attempt to index a nil value
stack traceback:
?: in function ‘modifyPlist’
?: in function ‘?’
?: in function <?:636>
The error is caused by either a space in your project folder or a space in the App Name field. That has been fixed in the latest daily build (2401). Nobody else is reporting the problem so make sure you are using the correct build. The problem doesn’t exist in the patched Public Build (2393a)
Mmh strange, it still doesn’t work for me.
I have no space in my project folder path, nor in the app name.
I even tried to generate a brand new Apple certificate + provisioning profile, but still get the same error.
Also tried with the latest build (2407), just in case, but no success.
What could I be doing wrong? :unsure:
@silverthorax, the spaces in the folder path only caused a build error and not a missing certificate error.
If you getting a missing certificate error, you need to check that you have the correct certificate installed (either developer or distribution) and you don’t have any other expired certificates (shows up in red in the keychain). In the keychain program you can use “iPhone” in the search field and delete anything that shows up in red.
Hello,
Just tried to build and having the same problem. Saying “certificate not installed” when trying to build. It’s a bit strange though because I used this just yesterday to submit an app, had the plist problem but that was solved and successfully uploaded to the store. I’m now trying to upload another and this error pops up, can’t even build now. Both my certificates are valid, my development cert runs out at the end of the month but that shouldn’t really matter?
Any help or advice please.
What is the error you are getting?
Hi Rob,
When I ‘Build for iOS’, the code signing Identity drop down list has the app greyed out and states:
(Certificate not installed) [name of app]
I didn’t think that Apple would let me download the provisioning profile it there was an error with my certificate.
Apologies!
I missed the earlier post which mentions downloading the updated 2393a Mac Simulator build. I’ve done that and all working great.
Thanks a mill!
i just download the latest build 2014.2411(Pro user) and still got the error when uploading app ERROR-ITMS-9000"invalid code signing…
@squrce, can you post the whole message? The fix that was addressed in 2393a and 2401 has to do with not being able to build with new profiles. They would be grayed out in the Corona SDK build screen and you would not be able to build at all. Since you’re getting an ITMS-9000 error, you’ve been able to build, so this is a different issue. We need to see the whole message.
Rob
The problem is the code signing error… i finally fixed it at the keychain. Recreate the certificate/provision profile at the apple developer site, remove old certificate at keychain & reinstall. Thanks Rob
Hey
I have a super large project that has to be built using the Corona 2014.1262 version. It is to much work right now to change to Graphics Engine 2.0, it is over 200 000 lines of code. But now I get the cert/provisioning issue discussed here and you released a version with an a on the end to fix this. BUT! Can you re-release a new 2014.1262 version so we can build the clients update please?
@andreas63, sorry but we have no plans to update the previous builds. Apple changed the rules and we can’t go back and support older builds to keep it compatible.
We released Graphics 2.0 in November, 2013, and most of our users have migrated to graphics 2.0. For those who didn’t migrate to the G2 APIs, we offer a V1 Compatibility mode that you can set in the config.lua.
Hey
I understand that and I tried to set the V1 Compability Mode on but everything on screen ends up in totally wrong positions and what I can see there is not easy way fixing this?
@andreas63, if everything is in the wrong position my guess is you haven’t set V1 compatibility mode correctly. If you are using setReferencePoint method, it will throw an error if you don’t have V1 mode enabled. You can also try using the anchorX or anchorY property on a display object. It should give you an error if you try to use it in V1 mode.
If you are using V1 mode, I’ve never heard of everything being mispositioned. I would need a simple example know what was going on. No one else has reported everything mispositioned in V1 mode and our Graphics 1 test app works fine in V1 mode.