Bug 5969 - CBCentralManager.ConnectPeripheral(peripheral, options) should accept null for argument 'options'
Summary: CBCentralManager.ConnectPeripheral(peripheral, options) should accept null fo...
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-07-03 17:18 UTC by Kirk Klobe
Modified: 2012-07-04 08:55 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 Kirk Klobe 2012-07-03 17:18:59 UTC
Objective-C allows the following syntax:

[central connectPeripheral:peripheral options:nil];

MonoTouch throws an exception when using:

manager.ConnectPeripheral(peripheral, null);

MonoTouch should allow this syntax.

The exception is:

System.ArgumentNullException: Argument cannot be null.
Parameter name: options
  at MonoTouch.CoreBluetooth.CBCentralManager.ConnectPeripheral (MonoTouch.CoreBluetooth.CBPeripheral peripheral, MonoTouch.Foundation.NSDictionary options) [0x0006a] in /Developer/MonoTouch/Source/monotouch/src/CoreBluetooth/CBCentralManager.g.cs:145
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-07-04 08:55:31 UTC

The next releases with this fix will be 5.3.6 and 5.2.13.

master: 9b8c71e9df59c5800963c03b246d386c1425de20
5.2-series: 63f0d3a5fad8a25ebce91492ecd79fce45f4c2ea