Waiting for Mavericks, I used Corona SDK on a Parallels Mountain Lion virtual machine. In my case in Mountain Lion already had this problem.
It happens from that updates to xcode 5
I’ve finally had the chance to test my app on an iPhone 5Gs with iOS 7. It works flawlessly without any problems.
So it’s really just the simulator from xcode.
This issue seems to get more confusing by the hour. 
At this point, it appears that it may be an issue with the Xcode Simulator? Related to (or maybe not related to) the latest Xcode update?
Brent
Hey Brent,
Yeah I totally know what you mean. I think this is super confusing. It is either xcode or corona.
Have you tried to compile a native written xcode app in the simulator?
I have been building and testing on devices with iOS 7, Xcode 5 on 10.8 for some time (multiple times a day pretty much every couple of days) and I’m not having this.
So if we’ve ruled out Mavericks as the issue, then it to me seems to be a problem with the Xcode simulator (and I almost never use the Xcode simulator) I dunno if my Mac is too old (2009 13" MBP with 4G memory) or if I don’t have enough memory, but it’s faster for me to build for device and use Xcode organizer to install the app and test it on the device than it is for Xcode to launch the simulator.
i have this problem after upgrade os to mavericks, using xcode5 GM. After that i upgrade the latest xCode from app store & still got the issues. i need to test it on xCode iOS simulator as i don’t have iPhone5.
When i’m on mountain lion and xcodeGM, my xcode simulator work well
Solved by me. I had an error in the code. Thanks for your interest. Sorry for the inconvenience
After an update to xcode, prove “Hello World” and it worked. My app still did not work. Look then and found. Little more I can say …
Hey everyone. The engineers did some testing on this last night and we cannot reproduce the problem. They have asked that you send in a project that this is failing on (keep it as simple as possible) and file a bug report. You can use the “Report a bug” link at the top of the page to do so.
We would like to get to the bottom of it. Please try and build our standard Hello World app and see if it has the problems too. Try different development vs. adhoc profiles and see if that has an impact too.
Please post your bug report numbers back in this thread for reference.
Thanks
Rob
Hi Rob,
Do you mean that I should send the Corona Project or an already compiled .app file to you via bug report?
The Project.
I also have this problem.
On my computer that I upgraded to Mavericks, the app crashes as soon as it opens on a device or xcode simulator.
It works fine on the corona simulator.
The exact same app builds and runs on all simulators and devices perfectly fine when built with my other computer that is still on mountain lion.
Even a barebones app that corona sdk generates for me crashes on the xcode simulator when built with Mountain Lion.
Any idea on why this is happening?
It’s very frustrating…
After more research, the post http://forums.coronalabs.com/topic/40246-app-crash-at-start-with-xcode5-and-ios-simulator/ describes whats going on.
I would love a solution!
I have the same problem. I just updated to Mavericks and now the app will not open in the Xcode simulator. It worked prior to the upgrade in the Xcode simulator. Works on my devices and the Corona Simulator. I think this is a Mavericks/Xcode incompatibility.
Really need a solution!
Thanks.
We are looking at this but none of us can reproduce the crash problem. Whenever you encounter a problem like this, please try building with the HelloWorld sample app to rule out any changes/errors in your project.
I built the simple default 2 tab application and it still wouldn’t run on the xcode simulators.
But I can run my apps on a physical device just fine.
The engineers have tracked it down and are looking into solutions, no ETA yet.
This does not impact device builds and you can build and test there where possible. I know this isn’t always possible (you have an iPhone but not an iPad for instance). Stay tuned.
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.
I am getting the “use of keychain-access-groups entitlement is not allowed (error code -67030)” error as well and can’t build for the iOS simulator or device.
Is there any workaround so that we can at least build for device in the meantime??