Bug 5581 - UIDatePicker's MaximumDate/MinimumDate should allow null set
Summary: UIDatePicker's MaximumDate/MinimumDate should allow null set
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.3.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
Depends on:
Reported: 2012-06-08 08:52 UTC by Jérémie Laval
Modified: 2012-06-08 10:27 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 Jérémie Laval 2012-06-08 08:52:59 UTC

A null (nil) value can be set on those two properties resulting effectively disabling minimum/maximum values. Right now it throws an ArgumentNullException.
Comment 1 Sebastien Pouliot 2012-06-08 09:49:18 UTC
Several other properties in this type seems to be missing their [NullAllowed]
I'll review that (while things rebuilds ;-)
Comment 2 Sebastien Pouliot 2012-06-08 10:27:52 UTC
Fixed (along with other cases)

master: 18d41aace0faa555b327c0b4f856e49e27f49001
5.2-series: 91f6913a538f9ce41d0b5975b0c823842bb44110

QA: unit tests added in both branches