Bug 9138 - Installing application Installation failed: AMDeviceInstallApplication returned: 0xe8008018
Summary: Installing application Installation failed: AMDeviceInstallApplication return...
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 6.1.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-12-27 05:36 UTC by ginogcostant
Modified: 2013-12-05 18:34 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description ginogcostant 2012-12-27 05:36:08 UTC
The following is a log that is generated when I run the cmd in the terminal /Developer/MonoTouch/usr/bin/mtouch --logdev. No even my old projects are having issues.



Dec 27 05:29:01 iPad-Development installd[30] <Error>: 0x2ffbe000 handle_install: Install of "/var/mobile/Media/PublicStaging/BarbiSize.app" requested by mobile_installation_proxy
Dec 27 05:29:01 iPad-Development installd[30] <Error>: 0x2ffbe000 MobileInstallationInstall_Server: Installing app Tummy2
Dec 27 05:29:01 iPad-Development installd[30] <Error>: Dec 27 05:29:01  SecTrustEvaluate  [leaf CriticalExtensions IssuerCommonName]
Dec 27 05:29:20 iPad-Development installd[30] <Error>: Dec 27 05:29:20  SecTrustEvaluate  [leaf ValidLeaf]
Dec 27 05:29:20 iPad-Development installd[30] <Error>: developer cert trust result = 5
Dec 27 05:29:20 iPad-Development installd[30] <Error>: 0x2ffbe000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.3iwelr/BarbiSize.app/BarbiSize: 0xe8008018
Dec 27 05:29:20 iPad-Development installd[30] <Error>: 0x2ffbe000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.3iwelr/BarbiSize.app
Dec 27 05:29:20 iPad-Development installd[30] <Error>: 0x2ffbe000 install_application: Could not preflight application install
Dec 27 05:29:20 iPad-Development mobile_installation_proxy[5288] <Error>: 0x39f2fb88 MobileInstallationInstall: failed with -1
Dec 27 05:29:20 iPad-Development mobile_installation_proxy[5288] <Error>: handle_install: Installation failed
Dec 27 05:29:20 iPad-Development installd[30] <Error>: 0x2ffbe000 handle_install: API failed
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-01-02 09:57:01 UTC
The error code 0xe8008018 indicates that it's because something is wrong with your provisioning profile, googling a bit reveals this error code: "The identity used to sign the executable is no longer valid".

This usually happens when your provisioning profile has expired.

Can you try to install a test app from Xcode to see what happens?
Comment 2 PJ 2013-11-19 17:04:45 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:34:54 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.