Bug 5563 - App fails to deploy to device after on device deletion
Summary: App fails to deploy to device after on device deletion
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-06-06 23:37 UTC by Felix Collins
Modified: 2012-07-22 17:31 UTC (History)
2 users (show)

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:

Description Felix Collins 2012-06-06 23:37:56 UTC
steps to repro:
1. run app under debugger
2. stop debugging
3. on device touch and hold app icon till wiggle achieved
4. touch x to delete app and data, confirm yes
5. try to run app from debugger (it says "app not found")
6. Unplug and replug device
7. try to run app from debugger... crash (deploy log at end of report)


MonoDevelop 3.0.2
	Mono 2.10.9 (tarball Mon May  7 20:25:51 EDT 2012)
	GTK 2.24.10
	GTK# (
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.2.1 (834)
	 Build 4D502
Mono for Android not installed
Monotouch: 5.2.12
Build information:
	Release ID: 30002000
	Git revision: 046db1bb0d9d438aa4d3468d66c6f963bc44c51a-dirty
	Build date: 2012-05-23 21:39:54+0000
	Xamarin addins: d99a1741642a336943d5607bdc1a09efa2ac3b86
Operating System:
	Mac OS X 10.7.4
	Darwin 11.4.0 Darwin Kernel Version 11.4.0
	    Mon Apr  9 19:32:15 PDT 2012
	    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64

  iPad2 5.1.1

  Version:	4.2.1 (4D502)
  Location:	/Developer
  Xcode:	4.2.1 (834)
  Instruments:	4.2 (4233)
  Dashcode:	3.0.2 (336)
  Mac OS X:
  10.6:	(10K549)
  10.7:	(11C63)
  iPhone OS:
  5.0:	(9A334)
  iPhone Simulator:
  5.0:	(9A334)


Please ensure your device is connected...
Connected to: Mokey
error MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
System.Exception: AMDeviceMountImage returned: 0xe8000073
at MonoTouch.Installation.Device.MountDeveloperImage () <0x00387>
at MonoTouch.Installation.Installer.FindApplication (MonoTouch.Installation.Device,string) <0x00017>
at MonoTouch.Installation.Installer/<LaunchApplication>c__AnonStorey5.<>m__5 (MonoTouch.Installation.Device) <0x0001b>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey3.<>m__2 (object,System.EventArgs) <0x000ef>
at MonoTouch.Installation.Device.NotificationCallback (MonoTouch.Installation.Device/am_device_notification_callback_info&) <0x0006e>
at (wrapper native-to-managed) MonoTouch.Installation.Device.NotificationCallback (MonoTouch.Installation.Device/am_device_notification_callback_info&) <0x0003f>
at (wrapper managed-to-native) MonoTouch.CoreFoundation.CFRunLoop.CFRunLoopRun () <0x00003>
at MonoTouch.CoreFoundation.CFRunLoop.Run () <0x0000b>
at MonoTouch.Installation.Installer.ExecuteWithSession (MonoTouch.Installation.Installer/Executor) <0x000cf>
at MonoTouch.Installation.Installer.LaunchApplication (string,System.Collections.Generic.List`1<string>) <0x00083>
at MTouch.Main2 (string[]) <0x03ccf>
at MTouch.Main (string[]) <0x0001f>
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-06-20 08:15:57 UTC
The error code 0xe8000073 means kAMDMobileImageMounterImageMoveFailed, which seems to happen once in a while (very rarely though). Unplugging / replugging the device usually fixes it, and it is not related to deleting the app as far as I can tell.

Can you consistently reproduce this error when following your steps?
Comment 2 Felix Collins 2012-07-22 17:31:38 UTC
Not worth following up...