Search Issue Tracker

Fixed in 2018.2.X

Fixed in 2017.3.X, 2018.1.X



Found in


Issue ID




Projects built with .NET 4.6, DateTime.Now always returns current UTC time regardless of your current local time



Reproduction steps:
1) Download and open project
2) Build and run "TimeTest1.unity" scene on an Android device
-- Notice that time printed is not same as device's current time (few hours difference)

Note: Issue is not reproducible with .NET 3.5 Scripting Runtime Version.

Reproduced with:
2017.3.0a4, 2017.2.0b7, 2017.1.0p4, 2017.1.0a3
5.5 and older versions do not support .NET 4.6 Scripting Runtime Version

Devices under testing:
Samsung Galaxy S7, Android 6.1
LG Nexus 5x, Android 7.0
Samsung Galaxy S4, Android 4.2.2
LG G3, Android 5.0
iPhone SE, iOS 9.3

Not reproducible on Standalone
Reproduced on Android and iOS

Fixed in: 2017.4.1f1, 2018.1.0b12, 2018.2.0a1

Comments (21)

  1. unity_1ySy-mI4kLUZ5w

    Aug 31, 2020 10:08

    Amazing project Thanks, i used for music site:

  2. unity_1ySy-mI4kLUZ5w

    Aug 31, 2020 09:54

    Amazing project Thanks, i used for music site:

  3. zereo1230

    Aug 28, 2020 01:56

  4. mercygaleria

    Jul 28, 2020 09:48;u=245304;u=19154;u=556429;;u=245305;;u=19155;u=556432;;u=556433;u=245302;;u=556434,,,,

  5. pragna01

    Jul 24, 2020 11:51

    Hey, This is a great article. I was searching for the same and I found the best content here. Thanks for sharing the info. keep on doing the great work.

  6. warfronts

    May 12, 2020 09:53

    Datetime.Utc now is off by -4min in a Samsung galaxy s5 device,
    Unity version: 2018.4.5f1.
    Tested with Redmi note 8 pro and DateTime.Utc now is OK.

  7. Fillmore

    May 15, 2018 16:15

    Anyone googling this issue?
    Fully fixed in the full release of Unity 2018.1.0f2

  8. MrSaoish

    Apr 16, 2018 20:49

    I can confirm that this issue is also presented on android build using 2017.3.1f1 with .NET 4.6 run time, and my device is Nexus 6p.

  9. Fillmore

    Apr 02, 2018 16:13

    Yes, this is confirmed fixed in b13

  10. bddckr

    Mar 23, 2018 08:31

    For anyone interested in what "future version" this is actually fixed in:
    The 2018.1.0b12 beta release notes list this bug as fixed.

    I assume this means it will be fixed with the final release of 2018.1 but Unity probably leaves that open until it's finalized and changes the status to note what version it's fixed in when it knows for sure I suppose.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.