Search Issue Tracker
Fixed in 2018.3
Fixed in 2018.2
Votes
0
Found in
2018.1.0f2
Issue ID
1044157
Regression
No
[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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error of NullReferenceException and black screen appears when opening new project in 2019.2.10f1 version
- [Vulkan] Wrong aspect ratio in fullscreen of Standalone build when selected screen resolution is not native
- [iOS 12] [Metal] IOAF code 4 error freeze because of tessellation shader
- 'A tree couldn't be loaded because the prefab is missing' error is thrown when importing package with Terrain Asset with Trees
- [Mac] Crash on ioAccelResourceListAddNewGroupAndResource when importing a large COLLADA model
craftostore
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: https://www.papayapr.com.au/