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 23734 on
GitHub or Developer Community 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
From Sept. 26, when you call DateTime.Now, it will return time with 1 hour less. Then, if current date on machine will be changed to 27 Oct., DateTime.Now will return correct value.
Steps to Reproduce:
1. On iOS 8, set timezone to +5 UTC Ekaterinburg.
2. Set current date on device to 26 September 2014.
3. Get current date and time like this:
4. Compare time on device with output, there will be 1 hour difference (error).
5. Set current date on device to 27 September 2014.
6. Get current date and time, it will be equal with time, displayed on device.
Tested in time zone +5 UTC Ekaterinburg (Russia) , on Mac OS X 10.9 and iOS 8.
My guess is that in DST logic, there is error when calculating current month (months are started not from 0)