Bug 1769 - Exception thrown when checking for updates
Summary: Exception thrown when checking for updates
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Updater ()
Version: 2.8.1
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-28 11:27 UTC by Neal
Modified: 2011-12-29 05:32 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 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 Neal 2011-10-28 11:27:42 UTC

I'm doing a MonoDevelop/Check for Updates and I get the exception below.  I'm using an iMac running LION.

System.NullReferenceException: Object reference not set to an instance of an object
  at MonoDevelop.Ide.Gui.BackgroundProgressMonitor+<OnProgressChanged>c__AnonStorey8C.<>m__109 (System.Object , System.EventArgs ) [0x00000] in /private/tmp/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/BackgroundProgressMonitor.cs:66 
  at Gtk.Application+InvokeCB.Invoke () [0x00000] in <filename unknown>:0 
  at GLib.Timeout+TimeoutProxy.Handler () [0x00000] in <filename unknown>:0
Comment 1 Jeffrey Stedfast 2011-12-22 15:10:40 UTC
Fixed by the patch for bug #1355
Comment 2 Saurabh 2011-12-29 05:32:54 UTC
We have verified this issue with MonoDevelop 2.8.5,it is working fine.

Kindly close this issue.