Bug 17480 - Getting exception "System.AggregateException" in Check for Update window
Summary: Getting exception "System.AggregateException" in Check for Update window
Status: RESOLVED DUPLICATE of bug 17452
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Updater ()
Version: 1.12.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Dominique Louis
Depends on:
Reported: 2014-01-29 04:37 UTC by narayanp
Modified: 2014-01-29 16:02 UTC (History)
3 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 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 narayanp 2014-01-29 04:37:30 UTC
Steps to reproduce:
1. Open VS
2. Click on Tools->Options->Xamarin.
3. Click on Check Now link either for iOS or Android.

Actual Result: It is showing error "Error Checking for Update". 

Expected Result: Check for Update window should displayed updates.

Supplement info:
Error details: https://gist.github.com/saurabh360/0e237356867c0d2f1e7b

Environment details:
All Windows
VS 2013/2012/2010
Xamarin for VS 1.12.164

Regression Status:
This is working fine with stable builds MTVS 1.8.365, X.Android
Comment 1 PJ 2014-01-29 16:02:23 UTC

*** This bug has been marked as a duplicate of bug 17452 ***