Bug 33449 - Passing null at NSNotificationCenter AddObserver
Summary: Passing null at NSNotificationCenter AddObserver
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-08-28 04:45 UTC by Sergey
Modified: 2015-08-28 08:39 UTC (History)
2 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 Sergey 2015-08-28 04:45:17 UTC
Passing null values for name, obj, queue, into a method:
public virtual NSObject AddObserver (string name, NSObject obj, NSOperationQueue queue, [BlockProxy (typeof(Trampolines.NIDActionArity1V18))] Action<NSNotification> handler);

cause ArgumentNullException.
But in apple documentation it should be possible: 
Comment 1 Sebastien Pouliot 2015-08-28 08:39:49 UTC
Thanks! Fixed in maccore/xcode7 3575cf2f9ca9a3577813c8393b6c26d05c75d8f0

Such errors should be less common in XI's future releases as Apple added
annotations in the Xcode7 SDK header files to specify where null is allowed (or