Bug 4227 - Incorrect result for DateTime.Now and TimeZone.CurrentTimeZone.GetUtcOffset() with Android 2.1
Summary: Incorrect result for DateTime.Now and TimeZone.CurrentTimeZone.GetUtcOffset()...
Status: RESOLVED DUPLICATE of bug 3520
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-04-04 10:05 UTC by Jonathan Clement
Modified: 2012-04-18 05:10 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Repro (10.82 KB, application/zip)
2012-04-04 10:05 UTC, Jonathan Clement

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 Jonathan Clement 2012-04-04 10:05:21 UTC
Created attachment 1620 [details]

DateTime.Now always return the UTC time and Time.CurrentTimeZone.GetUtcOffset() always return 0 on Android 2.1.

This does not seems to be device dependent. I get this result on an Sony Xperia X10, HTC Hero, Samsung Galaxy 550 and the emulator.

How to reproduce:

Set the 2.1 device or emulator timezone (in my case Eastern time).
Run the repro and look at the application output.

DateTime.Now and DateTime.UTCNow should not be the same. 
Time.CurrentTimeZone.GetUtcOffset() should not return 0.

Workaround :

// To get the right value for DateTime.Now
DateTime nowutc = DateTime.UtcNow;

DateTime correctedNow = TimeZoneInfo.ConvertTime(nowutc, TimeZoneInfo.Utc, TimeZoneInfo.FindSystemTimeZoneById(TimeZoneInfo.Local.Id));

// To get the right value for the current TimeZone
Comment 1 Atsushi Eno 2012-04-18 05:10:56 UTC
This looks like the same issue as bug #3520 which I believe is Android 2.1 bionic issue.

*** This bug has been marked as a duplicate of bug 3520 ***