iOS Installation Error: ApplicationVerificationFailed - ios

I have spent the last 6hrs searching the web for this bugs, I have read and tried many suggested solutions and still couldn't fix my problem. So lets hope someone can point me to the right direction this time.
I am using FDT to build AIR app, I can test it using iOS Simulator, I can package it and deploy to iTuneConnect but I just can't push it to my iPhone so I can test it. I am sure that my mobileprovision is correct (I check it with XCode 5), the app id is correct, and p12 is good also.
Here is the log I get from XCode console:
Mar 9 22:27:32 202-436-0338 installd[17] <Notice>: 0x10050c000 MobileInstallationInstall_Server: Installing app com.abcd.bht
Mar 9 22:27:33 202-436-0338 installd[17] <Error>: 0x10050c000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.WPRL4j/foo_extracted/Payload/BHT.app/BHT: 0xe8008015
Mar 9 22:27:33 202-436-0338 installd[17] <Error>: 0x10050c000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.WPRL4j/foo_extracted/Payload/BHT.app
Mar 9 22:27:33 202-436-0338 installd[17] <Error>: 0x10050c000 install_application: Could not preflight application install
Mar 9 22:27:33 202-436-0338 mobile_installation_proxy[142] <Error>: 0x10050c000 MobileInstallationInstallForLaunchServices: failed with -1
Mar 9 22:27:33 202-436-0338 mobile_installation_proxy[142] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil
Mar 9 22:27:33 202-436-0338 mobile_installation_proxy[142] <Error>: 0x10050c000 handle_install: Installation failed: Error Domain=LaunchServicesError Code=0 "The operation couldn’t be completed. (LaunchServicesError error 0.)" UserInfo=0x12c5121d0 {Error=ApplicationVerificationFailed, ErrorDetail=-402620395}
Mar 9 22:27:33 202-436-0338 installd[17] <Error>: 0x10050c000 handle_install_for_ls: API failed

have you installed previously any application on your device with the same bundle identifier?
it may also can cause the problem.
so you can try :
delete all adHoc apps from your phone.
clean build from Xcode.
double check that if you put correct bundle id and selected correct provisioning profiles.
your device added to provisioning profile? may be you created first provisioning profile, then added device in developer portal. (Recommended that check your device again in developer portal and create again adhoc profile.)
install again

Related

Got "This application does not support this device's CPU type" trying to run my application on iPhone 4S from Xcode

The application is built for armv7 architecture. I double checked binary header, and it contains 12 for CPU type and 9 for CPU subtype.
The application runs well on iPhone 5 but fails on iPhone 4S or iPad Mini. Both have iOS 7.0.3 installed. Xcode version 5.0. There are no specific processor requirements in plist.
See device console log below. Any ideas?
Nov 14 13:09:42 iPhone-4S installd[62] <Error>: 0x25d000 file_matches_my_arch: Can't map input file: /var/tmp/install_staging.7IZ38C/xxxx.app/xxxx
Nov 14 13:09:42 iPhone-4S installd[62] <Error>: 0x25d000 do_preflight_verification: Incorrect architecture at /var/tmp/install_staging.7IZ38C/xxxx.app
Nov 14 13:09:42 iPhone-4S mobile_installation_proxy[138] <Error>: 0x181000 MobileInstallationInstallForLaunchServices: failed with -1
Nov 14 13:09:42 iPhone-4S installd[62] <Error>: 0x25d000 install_application: Could not preflight application install
Nov 14 13:09:42 iPhone-4S mobile_installation_proxy[138] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil
Nov 14 13:09:42 iPhone-4S mobile_installation_proxy[138] <Error>: 0x181000 handle_install: Installation failed: Error Domain=LaunchServicesError Code=0 "The operation couldn’t be completed. (LaunchServicesError error 0.)" UserInfo=0x15d3fc90 {Error=IncorrectArchitecture}
Nov 14 13:09:42 iPhone-4S installd[62] <Error>: 0x25d000 handle_install_for_ls: API failed
I'm not sure about Xcode 5 but in Xcode 4 you have to make sure you have armv6 set as well.
See:
Why am I seeing "This application does not support this device's CPU type"?
Rebuilding the ipa (Xcode 6, same build configuration) solved this problem for me. Seems like a bug within the build process to me.

Please include the kCFBundleIdentifierKey in the options dictionary when installing an app

Anybody knows what this means?
Tried updating my app to ios 7 and tested it on iPad 2 and encountering these warning and error logs in Console:
Sep 24 16:23:56 iPad mobile_installation_proxy[118] <Warning>: LaunchServices: Please include the kCFBundleIdentifierKey in the options dictionary when installing an app.
Sep 24 16:23:56 iPad mobile_installation_proxy[118] <Warning>: LaunchServices: installing app for existing placeholder (null)
Sep 24 16:23:56 iPad installd[59] <Notice>: 0x2d5000 handle_install_for_ls: Install of "/var/mobile/Media/PublicStaging/THISAPP.app" requested by mobile_installation_proxy
Sep 24 16:23:56 iPad installd[59] <Notice>: 0x2d5000 MobileInstallationInstall_Server: Installing app com.<bundle>.<identifier>
Sep 24 16:23:56 iPad installd[59] <Error>: profile not valid: 0xe8008012
Sep 24 16:23:56 iPad installd[59] <Error>: 0x2d5000 install_embedded_profile: Could not install embedded profile: 0xe8008012
Sep 24 16:23:57 iPad installd[59] <Notice>: 0x2d5000 MobileInstallationInstall_Server: Staging: 0.08s; Waiting: 0.05s; Installation: 0.53s; LS Sync: 0.00s; Overall: 0.75s
Sep 24 16:23:57 iPad /usr/libexec/lsd[70] <Error>: Need to synchronize with MobileInstallation
Sep 24 16:23:57 iPad /usr/libexec/lsd[70] <Notice>: LaunchServices: Adding com.<bundle>.<identifier> to registration list
No Crash Logs are being recorded.
EDIT:
I have this in my info.plist
<key>CFBundleIdentifier</key>
<string>com.<bundle>.<identifier></string>
but it's basically com.site.my, I just edited the real name here.
I had the same issue, And was unable to install the ipa. It always ended with an error "Could not inspect the application package." and some warnings in device console
Feb 10 17:38:16 iPhone mobile_installation_proxy[356] <Warning>: LaunchServices: Please include the kCFBundleIdentifierKey in the options dictionary when installing an app.
Feb 10 17:38:16 iPhone mobile_installation_proxy[356] <Warning>: LaunchServices: installing app with unknown bundleID
.
.
Feb 10 17:38:16 iPhone installd[44] <Error>: 0x101bcc000 -[MIBundle _validateWithError:]: 28: Failed to load Info.plist from bundle at path
Feb 10 17:38:16 iPhone installd[44] <Error>: 0x101bcc000 + [MIInstallable installablesAtURL:packageFormat:userOptions:error:]: Failed to create bundle for …
After spending hours, I got it fixed by adding the "Application requires iPhone environment" in info.plist
<key>LSRequiresIPhoneOS</key>
<true/>
Did you check whether your bundle ID is in your plist
I had the same problem and it was because one of the pods I was using had a "Resources" directory. Fixing this pod following this advice resolved the issue.

iOS Ad-Hoc Install fails with proper provisions made

I have done this a dozen times successfully and cannot figure out what is wrong for this instance. I created the deployment certificate, added my devices, and then created my ad-hoc profile using the deployment cert and all devices.
I have a website that allows the user to install the profile and app. The app starts to install and gets to where it is almost done and then it just sits there. It fails for all devices with different flavors of iOS on them.
Any ideas what could be wrong? This is the console output where (altered) line 3 is bugging me. I think this is the primary failure point and I am investigating further. It works fine from my desktop.
Aug 5 09:08:29 MFI-Test-iPad-Mini installd[62] <Notice>: 0x3cf000 MobileInstallationInstall_Server: Installing app com.marketforce.Auditor
Aug 5 09:08:36 MFI-Test-iPad-Mini profiled[213] <Notice>: (Note ) profiled: Service stopping.
Aug 5 09:08:37 MFI-Test-iPad-Mini securityd[78] <Notice>: http asynchttp_timer_proc Timeout during GET http://ocsp.apple.com/ocsp-wwdr01/ThisHasBeenChangedInTheInterestOfSecurity%2BThisHasAlsoBeenAlteredForSecuritym67h1P0%3D.
Aug 5 09:08:37 MFI-Test-iPad-Mini installd[62] <Error>: entitlement 'keychain-access-groups' has value not permitted by provisioning profile 'Adhoc Distribution'
Aug 5 09:08:37 MFI-Test-iPad-Mini installd[62] <Error>: 0x3cf000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.nkJObR/foo_extracted/Payload/Auditor.app/Auditor: 0xe8008016
Aug 5 09:08:37 MFI-Test-iPad-Mini installd[62] <Error>: 0x3cf000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.nkJObR/foo_extracted/Payload/Auditor.app
Aug 5 09:08:37 MFI-Test-iPad-Mini installd[62] <Error>: 0x3cf000 install_application: Could not preflight application install
Aug 5 09:08:37 MFI-Test-iPad-Mini itunesstored[89] <Error>: 0x1c3e000 MobileInstallationInstallForLaunchServices: failed with -1
Aug 5 09:08:37 MFI-Test-iPad-Mini itunesstored[89] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil
Aug 5 09:08:37 MFI-Test-iPad-Mini lsd[166] <Warning>: LaunchServices: installation failed for app com.marketforce.Auditor
Aug 5 09:08:37 MFI-Test-iPad-Mini itunesstored[89] <Warning>: LaunchServices: installPhaseFinishedForProgress: com.marketforce.Auditor.Installing - <NSProgress: phase=Installing; state=Failed;
When I hit ad-hoc distribution errors, I have a couple troubleshooting steps to try to narrow it down.
Can you install just the provisioning profile? You should have either a developer or a distribution profile (depending, often times I install both to be sure).
Can you install the app via the iPhone Configuration Utility?
Answering those two questions will point you in the right direction at least. Good luck!
The app was originally created under a developer's appleID and the published in the Business To Business site. The developer left the company and the company created an appleID to be used for the company's development purposes. (Which is what should have been done to begin with).
The app was then transferred to the company's ID however the transfer didn't work right as it left the AppID under the old developer account so any attempt to use certificates and profiles against either account was doomed to failure while using the original AppID. To do any sort of internal deployment, a different AppID had to be created.
After Apple finally got the app transfer fully complete, all was good and the original AppID could once again be used.

iPhone app installation fails for enterprise distribution

An app downloaded/installed with enterprise distribution worked fine for long time until now, it suddenly stops with the following errors:
<Warning>: Killing xxx.OurApp for app installation
<Error>: 0x2ff99000 handle_install: Install of "/var/mobile/Media/Downloads/-9061050010711031503/-1709014265418617978" requested by itunesstored
<Error>: 0x2ff99000 MobileInstallationInstall_Server: Installing app xxx.OurApp
<Error>: profile not valid: 0xe8008011
<Error>: 0x2ff99000 install_embedded_profile: Could not install embedded profile: 0xe8008011
<Error>: Jul 10 18:10:47 SecTrustEvaluate [leaf CriticalExtensions IssuerCommonName]
<Error>: 0x2ff99000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.h6dNxf/foo_extracted/Payload/OurApp.app/OurApp: 0xe8008015
<Error>: 0x2ff99000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.h6dNxf/foo_extracted/Payload/OurApp.app
<Error>: 0x2ffcf000 MobileInstallationInstall: failed with -1
<Error>: 0x2ff99000 install_application: Could not preflight application install
<Error>: 0x2ff99000 handle_install: API failed
The weird part is, if we do a rollback of the website containing a link to a .plist and a .ipa to one that worked yesterday, it doesn't work any more. So the exact same .plist and .ipa that worked yesterday, today gives the error above.
The only think we can think of is that we increased the version number of the app from 1.0 to 1.3 in xcode before archiving (and enterprise distributing). But then we reverted back to 1.0 but nothing changed.
Anyone with similar problems?
Seemed to be some error in the new .plist. The problem was that since it went through half of the installation process it placed an half installed app and a broken profile on the phone. If removing both the profile and then the app, we could install the old app with old (correct) .plist

Xcode 4.5 - can't install developer .ipa files via iTunes

I had many times making a developer builds for testing purpose and everything was working fine. Was! After updating my Xcode to version 4.5 I can't install my developer builds via iTunes.
This situation is the same on every device I had in provision profile.
What I have and what I had checked double times with other developers to avoid personal mistake:
1) developer certificate
2) developer provision profile with added right devices
3) right build process
After success build of app me and other developers try to install it via iTunnes (10.7) but only error dialog appears that Synchronisation failed.
The very important info is, that I can build runnable app in xCode 4.2 and install it via iTunnes without any troubles with the same certificate and provision profiles
I can run the app directly on device if I run it via Xcode
Checked all apple's recommendation and I have all right: https://developer.apple.com/library/ios/#technotes/tn2009/tn2242.html
Checked lots of forums with similar issue and I have done many steps trying to reduce this problem starting with revoking ALL certificates, making new developers profiles with particular devices, cleaned tmp folders in Xcode together with build dir. I had delete all certificates, keys from KeyChain and import new ones. Deleted all provision profiles on device and install new one. Clean project, change a build architecture "armv", base SDK - Latest iOS 6.
Many thanks for your responce!!!
This is a part of log file from device (iPhone5 iOS 6.1)
Nov 7 23:31:04 lockdownd[29] <Notice>: 016ca000 __copy_itunes_value_block_invoke_0: com.apple.mobile.iTunes.store/PurchaseTypes -> (null)
Nov 7 23:31:09 installd[31] <Error>: 0x343000 handle_install: Install of "/var/mobile/Media/PublicStaging/denik4.ipa" requested by itunesstored
Nov 7 23:31:09 installd[31] <Error>: 0x343000 MobileInstallationInstall_Server: Installing app cz.newslab.denik
>
Nov 7 23:31:09 installd[31] <Error>: profile not valid: 0xe8008012
>
Nov 7 23:31:09 installd[31] <Error>: 0x343000 install_embedded_profile: Could not install embedded profile: 0xe8008012
>
Nov 7 23:31:09 installd[31] <Error>: Nov 7 23:31:09 SecTrustEvaluate [leaf CriticalExtensions IssuerCommonName]
>
Nov 7 23:31:09 mobile_assertion_agent[94] <Notice>: service_one_connection: Connection closed for client iTunes.
>
Nov 7 23:31:10 installd[31] <Error>: entitlement 'keychain-access-groups' has value not permitted by a provisioning profile
>
Nov 7 23:31:10 installd[31] <Error>: entitlement 'aps-environment' has value not permitted by a provisioning profile
>
Nov 7 23:31:10 installd[31] <Error>: entitlement 'application-identifier' has value not permitted by a provisioning profile
>
Nov 7 23:31:10 installd[31] <Error>: 0x343000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.yDZPNm/foo_extracted/Payload/denik.app/denik: 0xe8008016
>
Nov 7 23:31:10 installd[31] <Error>: 0x343000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.yDZPNm/foo_extracted/Payload/denik.app
>
Nov 7 23:31:10 installd[31] <Error>: 0x343000 install_application: Could not preflight application install
>
Nov 7 23:31:10 itunesstored[66] <Error>: 0x1786000 MobileInstallationInstall: failed with -1
>
Nov 7 23:31:10 installd[31] <Error>: 0x343000 handle_install: API failed
The important line is this one:
installd[31] : profile not valid: 0xe8008012
I've seen this error myself with one of our IPAs recently. It was solved by re-issuing the profile from the iOS Provisioning portal (simply make a simple change, undo it, then submit - that should regenerate the profile), updated the Xcode code signing identity to use the new profile, rebooted the device, and then tried again. It then seemed to install fine.
We weren't able to close in on a root cause of the issue, but once we'd gone through those steps we haven't seen it again.

Resources