iOS 26.6.2 Stopwatch Bug: Dynamic Island and Clock App Display Different Times | Potential Safety Concern

Question

Level 1

4 points

iOS 26.6.2 Stopwatch Bug: Dynamic Island and Clock App Display Different Times | Potential Safety Concern

I have repeatedly encountered a concerning issue with the native iOS Stopwatch on my iPhone 17, running iOS 26.6.2.

The Stopwatch displayed in the Dynamic Island sometimes shows a completely different elapsed time from the Stopwatch in the Clock app. In some instances, the Clock app has already been reset to 00:00.00 while the Dynamic Island continues displaying a separate time.

I have documented this behavior with screenshots.

Although this might appear to be a minor UI bug, inaccurate time measurements could have serious consequences when users rely on them for time-sensitive activities, including medication timing, physical activities or other safety-related situations.

I have not experienced any injury, but I believe this deserves investigation as a potential product safety issue.

My questions:

Has anyone else experienced this issue on iOS 26?
Is Apple aware of this recurring synchronization problem?
Is there an official fix or workaround?
How can this issue be escalated to Apple’s iOS engineering team for investigation?
I would appreciate confirmation from other affected users.

Device: iPhone 17

iOS: 26.6.2

Screenshots available.

Posted on Oct 26, 2026 1:06 PM

Reply

Answer 1

Oct 26, 2026 1:19 PM in response to Ed_zh

I can’t replicate the problem you describe. The value in the dynamic island always matches what I see in the clock app. I am using iOS 27.2, so you might try updating.

Ed_zh wrote:

I have repeatedly encountered a concerning issue with the native iOS Stopwatch on my iPhone 17, running iOS 26.6.2.

The Stopwatch displayed in the Dynamic Island sometimes shows a completely different elapsed time from the Stopwatch in the Clock app. In some instances, the Clock app has already been reset to 00:00.00 while the Dynamic Island continues displaying a separate time.

I have documented this behavior with screenshots.

Although this might appear to be a minor UI bug, inaccurate time measurements could have serious consequences when users rely on them for time-sensitive activities, including medication timing, physical activities or other safety-related situations.

I have not experienced any injury, but I believe this deserves investigation as a potential product safety issue.

My questions:1.

Has anyone else experienced this issue on iOS 26?

Don’t know, as I don’t have iOS 26.x

2. Is Apple aware of this recurring synchronization problem?

I’ve seen no indication that they have, but I’m not sure it is actually a synchronization problem, as yours is the first report I have seen.

3. Is there an official fix or workaround?

If there was an official fix it would be public, but have you reported it to Apple→Product Feedback - Apple

4. How can this issue be escalated to Apple’s iOS engineering team for investigation?

If you file feedback and many others do it will be investigated, but, as I’ve said, I’ve never seen any other reports

5. I would appreciate confirmation from other affected users.

Keep in mind that Apple Support Communities is not an official channel to Apple, it is a user-to-user technical support forum.

But I have a question for you: Why are you using a stopwatch for the uses you describe, instead of an alarm?

Reply