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.
I realised that the Starter could not see daily builds. I was just going to buy into the Basic but there will be no benefit there either then.
H’mm it is really frustrating/costly to be stopped using your products that you advertise as being able to publish to the app store, but now we cant do that if we stay up to date with Apple code and Corona public releases because of this bug.
I think there is a case here for your consideration of this solution being available in the daily build, to be quickly promoted to Starter and Basic level for public release, otherwise as you are not at the moment conforming to your ads. As I see it, I have to wait now for 3-4 months before I can publish and test on a device, maybe not even then?
I think this could be a business risk to your company if some Starter or Basic user has the funds to pursue this non-conformity…
May be check not the techy side of the business, but the legal!
Any way are there any technical alternatives in Corona for us Starter and Basic users to overcome this earlier?
@ibmprgmrsince1964, I think you mis-read what I said. I was not saying you will have to wait 3-4 **MORE** months. The current public build is about 2.5 months old. We’ve got some bugs to knock out of the new Graphics 2.0 engine before we can release a new public build. We will probably be freezing the branch soon and entering the deep testing phase. We can’t commit to an exact date because there are too many variables but it won’t be that much longer.
The benefit of a Basic plan is to get access to InApp Purchases. Daily builds are a benefit to Pro and Enterprise subscribers.
This particular bug only impacts the Xcode simulator with Mavericks. It does not impact device builds. So far everyone suffering issues with device builds have been able to solve their problem by cleaning out their keychain. You do not have to do XCode Simulator builds to build and deploy your app.
Are you experiencing a different issue?
Rob
Rob
Rob,
Thanks for a bit more clarity. It could be a variation/ additional problem. I had cleaned out keychain and even built new certificates/profiles etc.
I have gone and built direct to device and the app does not run/ but just flashes icon and then nothing. No console output at that stage, so I need to go and re-check via the XCode’s Organizer.
I had assumed this to be the same cause, so maybe not. I guess I need to check filenames for mismatch case typing or fonts( I am sure I have done this before but will now check again…).
Thanks
Alec
I recently too upgrade from Lion to OS Mavericks and Xcode. Same problems, mainly to do with some key signing issue. Cleared out Key chains and certs and all that and it hasn’t resolved anything. I’m with Alec on this, could a one time only daily build not be issued to at least starter subscribers to resolve this issue?
Evan
Well, have spent the day checking, changing, cleaning and any thing else I could think of or using suggestions from throughout the forums on this subject (excluding Pro or Enterprise build downloads-as I still have Starter).
I can now run on the xcode simulator (whoopie) but the app fails still trying to get installed on to the device!.
iTunes does not show the proper icon (default develop icon shown) and iTunes just sits there with ’ installing’ on the install button.
Sync shows copying, but never finishing install.
Using the Xcode organiser this shows that the code signature is missing/wrong.
So in my keenness what have I deleted? how//what do I re-create within the keychain utility? I have tried many variations so I think the only route to restore the code signature is remove xcode and re-install.
Would any one agree./disagree/ suggest another alternative?
I have tried recovery via the time machine but could not easily see what to select in the backup Libray/KeyChains folder and a little nervous I might corrupt something else.
Alec
This is now getting really confusing!
The problem is obviously something to do with the keychains and provisioning specification (sequence/definition) [a bug or lack of knowledge]
Now (down loading and re-installing Xcode 5 after cleaning all relevant keys yet again and then recreating them for about the fifth time) I cannot run the app now in the xcode simulator (the prior post time, the same app ran in the Xcode simulator OK!!!).
But now the app only runs on the device !!! First time for weeks.
After installing Xcode I cleaned out all keys and certs in my name and started afresh and recreated dev and distribution provision etc. In the provisioning there is also two activated by Xcode (default and one ap id i created). Plus a distribution provisioning, a dev provisioning, each I created. The device build used a default Xcode team dist code sign. I have tried various profiles sign id.s in the simulator and all fail the same way.
The Xcode simulator fails with a message about an unspecified device family!.
[DEBUG] SDK Root: <DTiPhoneSimulatorSystemRoot 0x100600920> path=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk version=7.0 name=Simulator - iOS 7.0
[DEBUG] using device family unspecified
Alec
PS The concern here is sometimes it works one way and then another different way. So are the ‘solutions’ stated above ‘permanent’ or just the luck of the draw as I find it varies depending on what day it is!
Help in understanding required here… Is this really due to the bug addressed by the latest daily build . Am I waisting my time or does all this help understand the bug???
I tried to load the exact same App onto my iPad and it failed to install.
The app installed ok on iPhone.
It will not run on Xcode simulator.
I am using provisioning profiles that include both devices
Curiously I have 3 DEV Provisioning Profiles defined and only 1 Distribution Provisioning Profiles.
The extra 2 are
a) Xcode install created ???
b) MyApp Id I created - but not referenced
Xcode Wild Card is used in all Profiles thus far.
Profiles
-
MyApp-Develop provisioning-Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active
-
MyApp-Distribution provisioning-ad hoc -Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active
- IOS Team * -Dev Provisioning -Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active-MANAGED BY Xcode
4.IOS Team com.MyApp * -Dev Provisioning-MyApp(com.myapp.*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active-MANAGED BY Xcode
All install ok on iPhone using iPhone Config Utility
However when installed on iPad only profile (1) and (2) are marked as vallid (3) and (4) are marked as not sign on the iPad only!
Therefore the Xcode organiser disabled the add application and it will not install. On iTunes I can add it but the iPad gives a msg unable to install and iTunes sits with ’ Installing’ displayed
I am on Xcode Version 5.0.1 (5A2053)
iPhone IOS 7.03911B511)
iPad IOS 6.1.2 (10B146) -this is left back level -wife wont allow update but also good base to validate on older IOS levels
is this the cause of failure to install now on iPad?
Alec
Alec, I’m sorry you’re having all of these problems. I wish there was some magic that would help.
The Mavericks-XCode5 issue shows when you look at the Mac’s Console app. Running 1202 you will get this error:
11/9/13 1:19:23.776 PM taskgated[13]: killed Orientation[pid 2489] because its use of the keychain-access-groups entitlement is not allowed (error code -67030)
This error occurs because pre-Mavericks, it was okay to run an app in the XCode simulator that was signed in a particular way. Mavericks changed this behavior and this is what we fixed in the daily builds, so that on Mavericks we changed how we sign the apps for the Simulator the way Xcode expects it.
We also have noticed that the IPhone Configuration Utility (which many people use to install apps to their device) seems to have issues on Mavericks. There is another thread about this. Engineering points to these two links:
http://forums.macrumors.com/showthread.php?t=1662524
https://discussions.apple.com/message/23562825#23562825
For workarounds. If you are using the iPhone Configuration Utility those links might help, but I highly recommend only using XCode’s Organizer to install things since it gives better error messages.
Now your issues are something that is different. There have been a few people after upgrading to Mavericks who had problems installing on device. So far you’re the only person that cleaning out the provisioning profiles and key chain hasn’t fixed. So let me try to summarize where you are:
1. You cannot build for the XCode simulator with 1202 on Mavericks. This is expected.
2. You can build for an iOS 7 iPhone with no difficulties.
3. You cannot build for an iOS 6 iPad.
Has the iPad been plugged into the Mac and from XCode’s organizer and you’ve told it to use that iPad for development?
Have you tried to create an AdHoc Distribution profile specifically for your app? I’ve never had a lot of luck using the Team profile. Making sure you have your devices in there. Download the profile and manually move it to ~/Library/MobileDevice/Provisioning\ Profiles/
Restart Corona SDK (Oh side note, after cleaning up all your keys and such, did you reboot?) and try building with the specific provisioning profile for your app?
Rob