Search Issue Tracker

Fixed

Fixed in 6000.0.49f1, 6000.1.3f1, 6000.2.0b1

Votes

0

Found in

6000.0.48f1

6000.1.2f1

6000.2.0a10

Issue ID

UUM-112014

Regression

No

DateTime.Now returned time is one hour behind on Android and iOS when GMT+1 timezones are selected

-

Reproduction steps:
1. Open the attached “DateTimeIssue“ project
2. On an iOS or Android device, set the timezone to one of the affected locations (London, Dublin, Casablanca, Rabat, Marrakesh)
3. Build and run the project on the iOS or Android device
4. On the device, observe the displayed time

Expected result: The shown time is correct
Actual result: The time is 1 hour behind

Reproducible with: 6000.0.48f1, 6000.1.2f1, 6000.2.0a10
Not reproducible with: 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Fixed in: 6000.0.49f1, 6000.1.3f1, 6000.2.0b1

Not reproducible with these devices:
macOS Sequoia 15.5 (M1 Max)

Reproducible with these devices:
VLNQA00123, Google Pixel 2 XL, OS:  11, CPU: Snapdragon 835 MSM8998, GPU: Adreno 540
VLNQA00363, Samsung Galaxy Z Fold 2, OS: 12, CPU: Snapdragon 865 SM8250, GPU: Adreno 650
VLNQA00639, Samsung Galaxy S25, OS: 15, CPU: Snapdragon 9 Elite, GPU: Adreno 830
VLNQA00624, iPhone 16 Pro, iOS: 18.5, CPU: Apple A18 Pro
VLNQA00394, iPhone 13 mini, iOS: 18.1, CPU: Apple A15 Bionic
VLNQA00359, iPhone 12 Pro, iOS: 17.6.1, CPU: Apple A14 Bionic

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.