Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
27
Found in
2017.1.0f3
Issue ID
943047
Regression
No
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 TimeTest.zip 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
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
cyliax
Sep 14, 2017 07:35
Same here. we need to build with 4.6 and even with 2017.1.1f1 DateTime.Now is not working as expected on mobile devices.