Bug 36271 - Deployment doesn't checksum Mono Runtime files etc.
Summary: Deployment doesn't checksum Mono Runtime files etc.
Status: ASSIGNED
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2015-11-26 02:49 UTC by Boris Spinner
Modified: 2016-01-12 16:26 UTC (History)
5 users (show)

Tags: BZCU
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 for Bug 36271 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
ASSIGNED

Description Boris Spinner 2015-11-26 02:49:45 UTC
So lately I noticed problems occuring on our team regarding incompletely downloaded files.
With files I mean those stored in 
AppData\Local\Xamarin.Android\Cache
and
AppData\Local\Xamarin

So, two things:

First, it occurs to me that the deployment process doesn't check those files for intactness (e.g. by checksum). So, once you've aborted any downloads, they won't be restarted and the IDE trys to work with incomplete Runtimes, SDKs, and so on.

Second, the IDE is not talking enough about downloading additional files. There's just the message "deploying" or "compiling" and what it actually does is downloading files like the Android API level specific Mono Runtime or zip files with Repositories in it etc. in the background. Problematic about this is the fact, more often than not it will compile/deploy faster after aborting the first compilation/deployment attempt, because of the first mentioned behavior. So the average user thinks it just freezed at some point and retrying the build solved it.

The combination of both leads to weird app/debugger behavior.
Comment 1 Boris Spinner 2015-11-30 14:36:26 UTC
This seems to be a duplicate of https://bugzilla.xamarin.com/show_bug.cgi?id=35397 ?
Comment 2 dean.ellis 2016-01-11 20:46:58 UTC
Boris, the second issue you mention is a duplicate of 35397 we are working on a way to check the downloaded zips are infact complete.

I'll take a look at the runtime deployment and see if we can repo an issue there when a build is cancelled.