Search Issue Tracker

Fixed in 2018.3

Fixed in 2018.2



Found in


Issue ID




[NET4.6] DateTime.ToLocalTime returns incorrect time in some timezones



To reproduce:
1. Open project
2. Set device timezone to Sydney, Australia; Adelaide, Australia or Wellington, New Zealand
3. Build and run on iOS or Android device

Expected vs Actual: returned DateTime.ToLocalTime is +1 hour of device stated time

Reproduced: 2017.4.1f1, 2017.4.4f1, 2018.1.0b12, 2018.1.2f1, 2018.2.0a1, 2018.2.0b6
Not reproducible in earlier versions because of bug #934382

Comments (1)

  1. 09ed60c0fc9e7c07503ffd03e246afc8?d=mm


    Aug 21, 2019 11:32

    We were trying to create a module using Unity3D for one of our client's restaurant in Sydney. When we tried including the Datetime.ToLocalTime attribute, it failed and returned incorrect results. We want to launch the app really soon to include Food, Restaurant, Beverage and Digital aspects of a restaurant. If someone finds a solution please reach us here:

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.