Battery usage timeline graph shows incorrect time labels in macOS 27

UI Frameworks SwiftUI
Train896 OP
Created
Replies 2
Boosts 2
Views 120
Participants 3

Description: The time scale values on the battery usage curve in macOS 27 are displayed incorrectly. The screenshot timestamp is 14:39:11, October 20. Under the "Last 24 Hours" tab for Battery Level and Screen On Time charts, the timeline shows usage extending past 21:00 on October 20. This timestamp does not match the actual current time. It appears the timeline axis failed to shift correctly as time progresses.

For comparison: a reference screenshot captured on macOS 26 at 09:30, August 8. Its battery usage timeline rendered correctly. The bottom time span covered August 7 to August 8, which is the expected and proper display behavior.

This bug only exists in macOS 27’s battery usage chart. The older macOS 26 implementation works correctly.

Device: MacBook Air M5 macOS version: macOS 27.2 RC

Replies  2
Boosts 2
Views  120
Participants  3
pedrojsoria OP

Same here.

Device: MacBook Air M4 macOS version: macOS 27.2
bug2null OP

Same issue here.

Environment:

  • Model: MacBook Pro (Mac17,9), Apple M5 Pro
  • macOS 27.2 (build 26B123)
  • Time zone: Asia/Shanghai (UTC+8), set correctly; system clock is accurate

Observation:
In System Settings > Battery > "Last 24 Hours", the Battery Level chart's
time labels are shifted by roughly 9 hours compared to the actual events.
The curve shape itself looks correct, only the x-axis labels are wrong.

Cross-check with pmset -g log (local time, +0800):

  • Charge rose from 80% to 100% between 2026-10-27 21:04 and 23:20
    -> chart shows this rise at around 07:00–08:00
  • Charge dropped back to the 80% charge limit at 2026-10-28 12:18
    -> chart shows this at around 21:00
  • At 12:30 local time, the right edge of the chart is already labeled ~21:00

So the chart's timeline extends ~9 hours past the current time, consistent
with the original report. Battery health is normal (cycle count 4,
max capacity 100%), so this appears to be a display bug in the chart only.

Screenshot attached.