Search Issue Tracker

Fixed in 2021.1

Fixed in 2018.4, 2019.4, 2020.2

Votes

0

Found in

2018.4

2018.4.16f1

2021.1

Issue ID

1288231

Regression

No

DateTimeOffset.Now has incorrect offset in Central European Time during daylight saving transition period

Mono

-

How to reproduce:
1. Open the attached "IncorrectLocalOffsetExample.zip" Project.
2. Build the Project on Android
3. In the device go to Android system date & time settings and disable automatic time setting
4. Set Time zone to the United States, Los Angeles (Pacific time, -7:00)
5. Set Date to October 24, 2020
6. Change time to 17:59
7. Set the time zone to Paris (GMT +2:00)
8. Wait for the time to become 2:00 local time according to the Android system clock
9. Run the app and observe values on the screen

Expected Behavior: Timezone changes from +2 to +1 GMT
// CET
// 10/25/2020 01:01:19 +00:00 <- correct
// 10/25/2020 02:01:19 +01:00 <- correct
// 10/25/2020 02:01:19 +01:00 <- correct
// 01:00:00 <- correct
// 10/25/2020 02:01:19 +01:00 <- correct

Actual Behavior: Timezone stays at +2 GMT
// CET
// 10/25/2020 01:01:19 +00:00 <- correct
// 10/25/2020 02:01:19 +02:00 <- incorrect
// 10/25/2020 02:01:19 +02:00 <- incorrect
// 01:00:00 <- correct
// 10/25/2020 02:01:19 +01:00 <- correct

Reproducible with: 2018.4.29f1, 2021.1.0a5

Reproducible with devices:
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
iPad Pro 12.9 (13.4.1)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.