@ingemar Thanks. I checked that thread out and followed the steps, but still no go.
@richared9 Didn’t experience that. Everything went smooth until trying to deploy it to development devices.
Signatures issues tend to occur because of an expired or expired and current certificates in the Keychain. If developer builds fail to sign but other builds work, your developer certificate is probably the issue. I would delete all developer certificates in the Keychain and download it again from Apple’s Provisioning portal. Have your Corona Pro account expire would not cause this issue.
We have tested Daily and Release builds, as well as Graphics 2.0 on Mavericks.
We also haven’t seen any Java issues with Mavericks, except for having to install Java again (which does require an Internet connection).
@Tom I have done as your suggested and still get the same issues. I noticed a message in the terminal saying that the developer certificate is found in both my user keychain and the system keychain under the same name. When i go to access the system keychain i cannot find any references to the developer certificate. I can only find it in the user keychain. Any idea what it is referencing?
iPhone Developer: JMarchalonis (WESD2MT813): ambiguous (matches “iPhone Developer: JMarchalonis (WESD2MT813)” in /Library/Keychains/System.keychain and “iPhone Developer: JMarchalonis (WESD2MT813)” in /Users/jmarchalonis/Library/Keychains/login.keychain)
We narrowed down the problem. CoronaSDK dose not sign Xcode apps so they can be used by users who don’t have Apple Dev accounts. The app bundle is built with an “embedded.mobileprovision” file if there are provisioning profiles on the system. It seems that Xcode5 expects the app to be signed if this file is included (the previous versions of Xcode ignored this file).
The error in the Xcode log when the app crashes in the Xcode simulator is:
“use of keychain-access-groups entitlement is not allowed (error code -67030)”
When we first tested the Xcode simulator on Mavericks, there were no provisioning files installed so everything worked correctly. We then installed provisioning files and tested on an actual device. We didn’t go back and test again on the Xcode simulator because we didn’t expect anything to change. Testing this again after installing the provisioning files cause the HelloWorld app to crash on the Xcode simulator.
We are currently looking into a fix for the problem.
This thread contains a discussion of a number of issues and it took time to understand exactly what is truly not working. Also, the term “simulator” can be confusing because that is what we call CoronSDK. We refer to Apple’s simulator as either Xcode Simulator or iOS Simulator.
I’m just wondering. We’re talking about two separate issues here, right?
One is the Xcode Simulator crash (which I can confirm that I also have), and one is that @jmarchalonis can’t install (drag) apps to his device in Xcode Organizer (which I can).
Sometimes I’ve seen that some certificates can’t be found until searched for.
Try this:
Start the Keychain Access app, and select “All Items” (found under “Category” on the left).
In the search field (upper right) type: iPhone
This will filter out all iPhone related keys.
You should see your iPhone Developer and iPhone Distribution certificates there and also see in which keychain they’re in (Keychain column on the far right). You only need Developer/Distribution certificates in the “login” keychain.
Delete any Developer/Distribution certificates you see in any other keychains.
Also delete any expired Developer/Distribution certificates you may see (ones with a little red icon).
Hope this helps…
The Xcode/Mavericks “keychain-access” bug (crash) has been fixed and available in build 1248.
We don’t feel the issue with dragging apps to Xcode Organizer is a Corona bug.
@Ingemar - I had exactly the same problem as jmarchalonis, with the same error in my terminal output. Your solution worked perfectly. Thanks for that, really appreciated.
I can’t sign anything either. No matter who many times I recreate my certificates, provisioning profiles, or start and stop Corona, the app will build but won’t go onto the device. It simple says “The application does not have a valid signature”…
Of course, it could not have happened at a worse time…
Richard
Richard, this sounds like a different issue. The problem above only impacts the XCode simulator on Mavericks with Xcode 5. Device builds have not been a problem.
Can you let us know more about the setup you have? OS, Version of Corona SDK, Xcode, etc? Can you post any messages showing up in your console log when you try to install the app?
Thanks
Rob
I had this exact issue last year, and when starting the Keychain Access app I couldn’t see any problems with my certificates. *However*, when I searched for the certificates using the search field in the upper right of the app window (ex. “iPhone”), an expired certificate showed up.
I posted the solution that worked for me back then, and you can find it a few posts up on this thread.
It helped another Corona user solve this problem. The important thing is that you must search for the certificate.
Looks like I’ve finally got past this issue. First a prefix: I’ve got over 200 apps published in the app stores, so signing an app and dealing with App ID’s, certificates, provisioning profiles, .P12 files for push, and more are all very routine to me. I do of course get caught in the occasional “expired certificate” or “invalid profile” loop but never to this extent. Here is what I ended up having to do this time to get past this problem, and what I think happened.
-
Completely delete every single certificate and profile I ever used
-
Clean all of my keychain access of any certificate in there (except the Apple certs)
-
Deauthorize my computer with Corona, and reauthorize it
-
Recreated a new dev cert, assigned it to an App ID, then created a new development provisioning profile
Somewhere in the mix of doing all of that (among a few reboots of my Mac) it all started working again.
I’m now a provisioning God…
lol
Thanks for the responses everyone!
Richard
Great to hear, Richard!
This thread has been idle for a bit, but I’ll give it a try nonetheless.
I’m having an issue with Corona Enterprise and Mavericks. Specifically, when I follow the ‘Building with Ant’ instructions in the Enterprise docs I get this at the end of the build:
./build.sh: line 96: ant: command not found
Not being a total doofus, I’ve tried various solutions to get ant installed (it seems Mavericks doesn’t install it):
- http://superuser.com/questions/610157/how-do-i-install-ant-on-os-x-mavericks (FAIL)
- http://stackoverflow.com/questions/19495610/error-executing-command-ant-on-mac-os-x-10-9-mavericks-when-building-for-andro (FAIL)
- …
I’m still hunting, but if anyone has overcome this please give me a heads up.
Thanks!
PS - This is what I get for upgrading… 
ant isn’t included in Mavericks anymore 
I used MacPorts and installed the ‘apache-ant’ port to solve this issue…
Thanks. I searched on the terms in your response and ended up going with this solution (not the same, but it worked to get ant installed):
http://gauravstomar.blogspot.com/2011/09/installing-or-upgrading-ant-in-mac-osx.html
So, now ant works, but I’m seeing other issues. Sigh, sadly I’ve used Windows for so exclusively for the last two years that my ‘Linux/Unix/OS X’ kung fu is very weak.
Regardless, thanks again for the quick response!
What other issues are you having Ed?
I’m not sure if it’s related, but I cannot publish to the app store any longer no matter what I try. I persistently get :
Error ITMS-9000 :Invalid Code Signing entitlements. The entitlements in your app bundle signature do not match the ones that are contained in provisioning profile. According to the provisioning profile, the bundle contains a keyvalue that is not allowed “[BG2J43EA88.com.coronalabs.template]’
And I’ve tried everything. Details are in this thread: http://forums.coronalabs.com/topic/41367-comcoronalabstemplate-app-store-publishing-error/#entry215238
Richard