Search Issue Tracker
Fixed
Fixed in 2022.2.21f1, 2023.1.0b18, 2023.2.0a17
Votes
1
Found in
2022.2.16f1
2023.1.0a11
2023.1.0b12
Issue ID
UUM-33155
Regression
Yes
”DateTimeNow” reports the wrong date on mobile devices when having a specific Time Zone
How to reproduce:
1. In the device settings, change Time Zone to Amsterdam
2. Build And Run the user’s attached “iOS_Clock_Issue.zip” project on a device
3. Observe the “DateTimeOffset.Now“ in logs
Expected result: Logged time is the same as in the device and “+2” is at the end
Actual result: Logged time is one hour early compared to the device and “+1” is at the end
Reproducible with: 2022.2.0a9, 2022.2.16f1, 2023.1.0b12, 2023.2.0a11
Not reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.2.0a8
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
VLNQA00520, Samsung Galaxy S22 (SM-S901U), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
Notes:
No repro with Lithuania Time Zone
Not reproducible in the Editor and macOS standalone Player
The issue started after Daylight Saving Time
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
- Articulation Bodies spawn at the same point on a Spline when entering the Play mode
- [HDRP] Mip Map Debugging View turns White if there are Directional Lights in the Scene
- RenderDoc Capture Frame can't be completed after Particle System is simulated
- Editor crashes when attempting to connect the client machine to the host machine
- CameraDepthTexture is flipped upside down when URP is rendering without the final blit
Resolution Note (fix version 2023.2.0a17):
Fixed in: 2023.2.0a17
Resolution Note (fix version 2023.1.0b18):
Fixed in: 2023.1.0b18
Resolution Note (fix version 2022.2.21f1):
Fixed in: 2022.2.21f1