Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 28887 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 10674 [details]
When I run the attached sample I get different values if I run under OS X Yosemite or Other e.g. Mavericks
m_aPicker= new NSDatePicker(new CGRect(100,100,200,200 ));
m_aPicker.DatePickerElements = NSDatePickerElementFlags.YearMonthDateDay;
m_aPicker.DatePickerMode = NSDatePickerMode.Single;
m_aPicker.TimeZone = new NSTimeZone("UTC");
m_aPicker.DatePickerStyle = NSDatePickerStyle.ClockAndCalendar;
m_aPicker.Bordered = false;
m_aPicker.DateValue = DateTimeToNSDate(DateTime.Today);
On Yosemite it will show 8 April 2015
On Mavericks or below I get 7 March 2015
Apple Bug ? Xamarin Bug ?
I cannot see anything in the documentation that suggests differences ?
The 100% way to determine who's "fault" this is to compare it to an objective-c version:
I believe this is a Cocoa bug unless proven otherwise :) We do very little in the binding code related to dates.
Created attachment 10675 [details]
Objective C Test
Just tried the sample you suggested and both Mavericks and Yosemite are showing correctly, Which is not what I am seeing as Xamarin version.
Hmm. We'll have to do some digging if C# is different than obj-c.