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??
The Xcode/Mavericks “keychain-access” bug has been fixed and available in build 1248.
Thanks everyone for posting your information about this bug.
Any resolution on this error -9000: “The bundle [Bundle ID, ex: com.myapp.mobile] at bundle path ‘Payload/[My App Name].app’ is not signed using an Apple submission certificate.” at SoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)
when using App loader to upload an app.
If the app is compiled on a non mavericks the validation tool fails and Corona spawns a warning
warning: Unable to run the lipo command: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/lipo: can’t figure out the architecture type of: [APP PATH/APP]
(-19034)
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/lipo: can’t figure out the architecture type of: [APP PATH/APP]
- (null)
warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
Executable={APP PATH/APP]
codesign_wrapper-4.1: using Apple CA for profile evaluation
AssertMacros: (__builtin_constant_p(fat.magic) ? ((__uint32_t)((((__uint32_t)(fat.magic) & 0xff000000) >> 24) | (((__uint32_t)(fat.magic) & 0x00ff0000) >> 8) | (((__uint32_t)(fat.magic) & 0x0000ff00) << 8) | (((__uint32_t)(fat.magic) & 0x000000ff) << 24))) : _OSSwapInt32(fat.magic)) == 0xcafebabe, file: codesign.c, line: 249
AssertMacros: code_signatures, file: codesign_wrapper.c, line: 945
- (null)
and if the same code, using the same certificates are build on a Mavericks machine, CoronaSDK has no errors it even offers to upload the app to the App Store, however it bails with metadata not found and the file not found. Manually trying to upload to the App store results in the Error -9000 mentioned above.
The certificates are all created fresh and are fine, ie. have not expired or whatsoever.
Would the fix be available to starter users or just those with a subscription?
As it stands now, building is totally unusable (public build 1202) and the only way to use it is to buy a subscription, is it?
I’m confused about where you’re seeing this error. Are you saying building a distribution build with non-mavericks (e.g., Mt. Lion) OS with build 1202 gives you this error? I haven’t seen anyone else report problems with distribution builds.
The Mavericks/Xcode fix only affects the Xcode Simulator and is only available in Daily Builds. We can’t fix the Public Release build.
@Tom,
just wanted to say that the new daily build solved my problem. I can finally test my app on iOS7 ! Thank you!
Mavericks.
XCODE. 5.0.1
Daily Build: Version 2013.1251 (2013.11.1)
Still having issues. Was this resolved or not. When I want to load Helloworld on to device it gives" The application does not have a valid signature.
Console
Nov 3 16:16:48 SecTrustEvaluate [leaf CriticalExtensions IssuerCommonName]
Nov 3 16:16:48 iPad installd[54] <Error>: 0x283000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.Z1vjvp/HelloWorld.app/HelloWorld: 0xe8008019
Then on other app
There was an internal API error.
Console"
0x3d7b3b88 MobileInstallationInstall: failed with -1
Nov 3 16:18:46 iPad mobile_installation_proxy[2796] <Error>: handle_install: Installation failed
Nov 3 16:18:46 iPad installd[54] <Error>: 0x283000 install_application: Could not preflight application install
Nov 3 16:18:46 iPad installd[54] <Error>: 0x283000 handle_install: API failed
Nov 3 16:19:46 iPad installd[54] <Error>: 0x283000 MobileInstallationCheckCapabilitiesMatch_Server: desired capabilities is not an array or dicitonary
Nov 3 16:19:46 iPad installd[54] <Error>: 0x283000 handle_check_capabilities: API failed
Nov 3 16:19:46 iPad mobile_installation_proxy[2801] <Error>: 0x3d7b3b88 MobileInstallationCheckCapabilitiesMatch: failed with -1
Nov 3 16:19:46 iPad mobile_installation_proxy[2801] <Error>: handle_check_capabilities: Check Capabilities failed"
Please help.
This particular issue impacts the XCode simulator and it is a keychain related issue. @Sadsack what you are probably encountering a bad certificate in your keychain that is causing this issue. You should be able to delete all your development keys and certificates, clear out your provisioning profiles and then generate new certificates and keys and then recreate the provisioning profiles and download them anew.
Several people have done this and it solved the problems.
This isn’t a Corona issue as much as it is an interaction between Mavericks, XCode5 and your keychain.
Hi Rob
I have tried that. I have cleared all my keychains, reloaded and created new Keychains. In terminal rm all prevoise provision profiles and add the new one. The HalloWorld still does want to be uploaded on my device.
I have tested on two different Mac PC. And both of them give this issue.
Nov 3 20:56:39 iMacs-iPad wifid[15] <Notice>: WiFi:[405197799.878354]: new locale: , locale:
Nov 3 20:56:42 iMacs-iPad mobile_installation_proxy[128] <Warning>: LaunchServices: Please include the kCFBundleIdentifierKey in the options dictionary when installing an app.
Nov 3 20:56:42 iMacs-iPad mobile_installation_proxy[128] <Warning>: LaunchServices: installing app for existing placeholder (null)
Nov 3 20:56:42 iMacs-iPad installd[60] <Notice>: 0x2cc000 handle_install_for_ls: Install of “/var/mobile/Media/PublicStaging/HelloWorld.app” requested by mobile_installation_proxy
Nov 3 20:56:42 iMacs-iPad installd[60] <Notice>: 0x2cc000 MobileInstallationInstall_Server: Installing app HelloWorld
Nov 3 20:56:43 iMacs-iPad installd[60] <Error>: 0x2cc000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.eCKcrZ/HelloWorld.app/HelloWorld: 0xe8008019
Nov 3 20:56:43 iMacs-iPad installd[60] <Error>: 0x2cc000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.eCKcrZ/HelloWorld.app
Nov 3 20:56:43 iMacs-iPad mobile_installation_proxy[128] <Error>: 0x201000 MobileInstallationInstallForLaunchServices: failed with -1
Nov 3 20:56:43 iMacs-iPad mobile_installation_proxy[128] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil
Nov 3 20:56:43 iMacs-iPad installd[60] <Error>: 0x2cc000 install_application: Could not preflight application install
Nov 3 20:56:43 iMacs-iPad mobile_installation_proxy[128] <Error>: 0x201000 handle_install: Installation failed: Error Domain=LaunchServicesError Code=0 “The operation couldn’t be completed. (LaunchServicesError error 0.)” UserInfo=0x1657ee60 {Error=ApplicationVerificationFailed, ErrorDetail=-402620391}
Nov 3 20:56:43 iMacs-iPad installd[60] <Error>: 0x2cc000 handle_install_for_ls: API failed
for me - only since Maverick.
Hi @brindleware,
@roman85 seems to have solved this by using the latest daily build. Have you tried the same?
Did you clear off all provisioning profiles on the actual device, clear out and re-generate new certificates and provisioning profiles in the Apple Dev Center, sync the device with your computer, check that all of the new profiles are “active” and marked with a green dot, then re-started the Corona Simulator to build?
Brent
Start system user will have no access to daily builds.
So are we stuck until a new starter system build is release (when?).
Thanks
Alec
Hi @ibmprgmsince1964, you are correct, both the Starter and Basic tier do not get access to daily builds. We don’t have a set schedule for when we put out public builds, but we’ve been doing so in the 3-4 month range recently. And we have not announced a date for the next one yet.