Bug 3095 - Debug/Run after switching devices does not upload the new app
Summary: Debug/Run after switching devices does not upload the new app
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-01-26 16:00 UTC by Jackson Harper
Modified: 2012-10-15 18:43 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 FIXED

Description Jackson Harper 2012-01-26 16:00:46 UTC
Using two devices:

1. Build, upload and debug the app on device A.
2. Stop debugging.
3. Unplug A
4. Plug in device B
5. Debug

The app will not be uploaded to device B, so you will either be debugging an old or non-existant version.
Comment 1 Mikayla Hutchinson [MSFT] 2012-01-26 16:35:13 UTC
MD sets a flag file to indicate that the app has been uploaded so that it does not get uploaded again until it is rebuilt, because uploading is quite slow. If MD could detect the ID of the attached device, then this flag could be per device, which would fix the problem.

A similar problem is when the user manually removes the app from the device. To fix this, MD would have to be able to detect the presence of the app on the device.
Comment 2 Jackson Harper 2012-01-26 16:42:07 UTC
Yeah, the removed app thing is more understandable. However, it is a pretty common thing to do. Since so many apps have 'first run' code, I remove my app very frequently while debugging.
Comment 3 Jeffrey Stedfast 2012-10-15 18:43:17 UTC
It looks like this has been fixed already with an mtouch -isappinstalled command that MD issues to determine if it needs uploading.