Bug 32150 - Error: The request was aborted: The operation has timed out.
Summary: Error: The request was aborted: The operation has timed out.
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Device Manager ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-07-20 12:49 UTC by Jon Douglas [MSFT]
Modified: 2015-10-07 11:21 UTC (History)
2 users (show)

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

Logs (3.29 KB, application/x-zip-compressed)
2015-07-20 12:49 UTC, Jon Douglas [MSFT]

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 Jon Douglas [MSFT] 2015-07-20 12:49:19 UTC
Created attachment 12115 [details]


I downloaded and installed the Xamarin Android Player. I followed the instructions given in the Xamarin tutorial for Xamarin Android Player. After installation, I am asked to run the player. And select the emulator I wish to use and download it. When I try the same, it gives me the following error.

Error: The request was aborted: The operation has timed out.

1. Logs Attached

2. OS – Windows 8 enterprise. 64 bit.

3. Yes it is a company managed domain.
Comment 1 Mark Simpson 2015-09-28 06:44:23 UTC
Is this still an issue in the current version (0.6.1)? There has been a lot of chance to the download code.
Comment 2 Mark Simpson 2015-10-07 11:21:56 UTC
We believe the changes in the newer versions have fixed this, please reopen if this is not the case.