Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2017.2.3p1
Issue ID
1087719
Regression
No
Varied timezones available on Mac and Windows
To reproduce:
1. Open attached project "case_723483-TimezoneError-Win.zip"
2. Open "scene.unity" scene
3. Enter Play mode
4. Observe the console
Expected result: MacOS and Win machines have the same number of time zones showed in the console
Actual result: MacOS machine has a lot more time zones shown in the console
Test results:
2017.4.12f1:
MacOS:
.NET 3.5 - 464
.NET 4.6 - 424
Win10:
.NET 3.5 - 0
.NET 4.6 - 137
2018.2.11f1, 2018.3.0b5, 2019.1.0a4:
MacOS:
.NET 3.5 - 464
.NET 4.x - 487
Win10:
.NET 3.5 - 0
.NET 4.x - 137
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.1):
.Net 3.5 returning zero timezones on windows has been fixed in the new .net 4.x.