Why Your Apple Watch Alarm Didn't Wake You Up, and the iOS Update That Finally Fixed It
iOS 26.4 added an 'Always Play on iPhone' toggle that stops alarms from routing silently to a watch you're wearing to bed. It's off by default, and it only fixes the routing failure, not oversleeping in general.
In this article5 sections
Why didn’t my Apple Watch alarm wake me up, and how do I fix it in iOS 26.4? Because on a paired iPhone and Apple Watch, an alarm can be routed to sound on only one of the two devices, and when that device is the watch, the “sound” is a haptic tap that’s easy to sleep through or that never fires audibly at all if the watch is silenced. iOS 26.4, released around April 28, 2026, added a toggle called Always Play on iPhone, in the Health app under Sleep → Alarm Options, that forces the phone to play an audible alarm alongside the watch. It’s off by default, so updating to 26.4 alone doesn’t fix anything — you have to go turn it on.
Why didn’t my Apple Watch alarm wake me up?
The alarm almost certainly did fire. It just fired somewhere you weren’t positioned to notice it. iOS and watchOS coordinate which paired device handles an alert so the same notification doesn’t buzz and ring on both simultaneously every time — that coordination is a real feature for texts and calls, where getting pinged twice is annoying. Apple extended the same logic to alarms. When the watch is on your wrist and appears to be the device you’re actively using (worn, unlocked, screen recently woken), the system can hand the alarm to the watch alone, as a haptic tap sequence, and skip the phone’s speaker entirely.
That’s fine if the tap wakes you. It’s a silent failure if it doesn’t — the watch is in Silent Mode, the tap is too light to register through a heavy sleep stage, or the watch has slipped off or lost charge overnight without your noticing before bed. Unlike a missed call that at least leaves a voicemail and a badge, a watch-only alarm that nobody feels leaves no trace at all: no sound played, nothing wrong logged, just a person still asleep at the time they meant to be up.
What is the “Always Play on iPhone” setting in iOS 26.4?
It’s a toggle, reported by 9to5Mac and BGR when iOS 26.4 shipped in late April 2026, that overrides the single-device routing described above. With it on, the iPhone plays its own alarm sound out loud at the same time the watch does whatever it does — haptic, sound, or both, depending on the watch’s own settings. The phone stops deferring to the watch as if the watch were the only device that mattered.
It’s worth being precise about where this lives, because it’s easy to look in the wrong app. It isn’t a Clock app setting, and it isn’t buried in the Watch companion app’s alarm settings either — both would be the more obvious guesses. Apple placed it in Health → Sleep → Alarm Options, tied to the Sleep schedule and wake alarm that the Health app already manages, since that’s the alarm path most likely to be set while wearing the watch to bed in the first place.
How do I turn on Always Play on iPhone?
- Open the Health app on iPhone.
- Tap Browse, then Sleep.
- Tap Alarm Options.
- Toggle on Always Play on iPhone.
That’s the entire sequence — no restart, no re-pairing. Because it’s off by default, a phone that’s already running iOS 26.4 gets none of the benefit until someone opens Health and flips it manually, which is worth checking directly rather than assuming an update handled it. It’s also worth checking again after any future iOS update; Apple has no stated pattern yet for whether new default-off settings like this one get reset or preserved across major version jumps, and confirming the toggle’s actual state costs ten seconds.
Does this fix drain my iPhone or Apple Watch battery faster?
No meaningful difference. Both devices already run an independent clock and already wake briefly to evaluate whether an alarm is due — that overhead exists regardless of which device ends up playing sound. What changes with the toggle on is that the phone’s speaker fires for the alarm’s duration instead of staying silent, and a speaker burst of well under a minute is a rounding error against what an iPhone or Watch already spends overnight on Bluetooth advertising to stay paired, on-wrist sensor logging, and background app refresh. If you’re troubleshooting a genuinely fast overnight battery drain, look at those first; this setting isn’t a meaningful contributor either way.
Does fixing the routing bug guarantee I won’t oversleep?
No, and it’s worth being specific about why not. This setting fixes exactly one failure mode: the alarm sounding somewhere you couldn’t perceive it. It does nothing for what happens after Focus modes are already correctly configured and every device is playing sound on schedule — hearing the alarm and turning it off half-asleep, hearing it and going back to sleep in the same motion, or genuinely sleeping through a sound that was objectively loud and correctly routed. Apps that need an alarm to survive Do Not Disturb and Focus modes at the system level, the way this iOS fix is meant to, lean on the Critical Alerts entitlement Apple grants case by case — a related but separate mechanism from the watch-vs-phone routing this toggle addresses. And comparing the watch and the phone as alarm devices in general surfaces other gaps this particular fix doesn’t touch, like a dead watch battery or a watch left on the charger overnight instead of the wrist.
The closest everyday analogy is a phone call that rings on a device you didn’t have on you and goes to voicemail: the call didn’t fail, the routing decision about where it would ring did. iOS 26.4 fixes the routing decision for alarms. It has no opinion on, and no way to enforce, what a person does in the several seconds after the sound reaches them.