Search Issue Tracker
Duplicate
Votes
4
Found in
2017.1.0p1
Issue ID
934382
Regression
No
Time zone conversions fail on iOS, Android and WebGL devices when using the Experimental (.NET 4.6 Equivalent) runtime
.ToLocalTime() fails to convert time on iOS, Android and WebGL.
.ToLocalTime() works as expected on Mac and Windows standalone builds or when Scriptable Runtime version is set to Stable (.NET 3.5 Equivalent).
Steps to reproduce:
1. Open User's attached project (TimeZoneConversion.zip)
2. Build and Run scene on iOS, Android or WebGL
3. Check Console logs
Expected output: UTC: 7/24/2017 8:20:28 AM, local: 7/24/2017 11:20:28 AM
Actual output: UTC: 07/24/2017 08:23:33, local: 07/24/2017 08:23:33
Reproduced with: 2017.1.0p1.
Not reproduced with: 5.6 and earlier (no Experimental (.NET 4.6 Equivalent) feature)
Tested with: iPod 6th gen iOS 10.2.1, Samsung Galaxy S7 Android 6.0.1.
Comments (2)
-
phila666
Oct 25, 2017 20:02
more specifically, it appears that all the timezone and datetime classes in .net 4.6 thing they are in UTC as their local zone, which becomes problematic is you are dealing with say, a native time picking object, which has the local timezone set correctly, so they do not agree.
-
phila666
Oct 25, 2017 19:58
Still broken on 2017.2 using .net 4.6
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #943047