The morning after an iOS update is a bad time to discover your alarm didn't fire. The instinct is immediate and reasonable: the update broke it. Sometimes that's true. Usually it isn't — what actually happened is that the update disturbed something around the alarm, and the alarm itself was innocent.
Here's how I work through it, from the checks that take ten seconds to the ones that mean something's genuinely wrong.
What an Update Actually Does to Your Alarms
A normal over-the-air update is less dramatic than it feels. Your Clock alarms are stored data — they come through the update intact, with their times, repeat schedules, labels and sounds. The phone restarts as part of the process, which occasionally clears up unrelated weirdness as a bonus.
What the update can change:
- The state of background processes and permissions. Third-party apps get relaunched fresh, and anything relying on background behaviour has to re-establish it.
- Which settings screens exist and what they're called. Features get moved, renamed, split, or given new defaults. A toggle you set two years ago may now live somewhere else, or may have a new sibling setting that overrides it.
- Post-update setup prompts. The first-run screens are easy to tap through without registering what you agreed to — including notification and Focus-related choices.
- Audio routing. Bluetooth devices reconnect after the reboot, sometimes in a different order.
What it very rarely does is delete an alarm. So start by confirming that.
Check 1: Look at the Alarm Before You Change Anything
Open the Clock app. Is your alarm still there? Is its toggle on?
If it's gone, you're probably dealing with a restore or transfer rather than a plain update (see below). If it's there but switched off, and it's a non-repeating alarm, it may simply have fired and ended normally — that's what one-off alarms do. If it's there and armed, the alarm object is fine and the problem is elsewhere in the chain.
Also check whether you're looking at the alarm you think you are. If your Clock app shows a separate sleep or wake-up section above the alarm list, you have both a sleep schedule and Clock alarms running, and updates are a great time to discover you've been editing the wrong one for months. That whole mess is untangled in the Sleep Focus and Sleep Schedule post.
Check 2: If You Restored or Transferred, Assume Nothing
This is the single biggest source of "the update broke my alarm" reports, and it's usually not an update at all. Setting up a new iPhone, restoring from a backup, or transferring directly from an old device is a much bigger operation than a software update, and alarms are among the things that can come across in an unexpected state — present but disabled, present with a sound that no longer exists on the new device, or absent entirely.
If you've done any of those recently, don't debug. Rebuild. Delete the alarms in the list and create the ones you need from scratch, picking the sound explicitly. It takes a minute and eliminates a category of stale state you can't easily inspect.
Check 3: Re-Check Focus, Notifications, and Volume
Three things worth confirming after any significant update:
Focus modes. Scheduled Focus modes survive updates and sometimes come back with adjusted behaviour. Clock alarms ring through Focus modes by design, so this matters most if you use a third-party alarm — check that the app is allowed to notify you during whatever Focus is active overnight.
Notification permissions. Again, mainly a third-party concern. Open the notification settings for your alarm app and confirm it's still allowed to deliver alerts, with sound, on the Lock Screen. A "reset" of these in an update is uncommon but a mis-tapped setup prompt isn't.
Volume. The ringer and alerts level is the one your alarm uses, and it's worth eyeballing the slider directly rather than trusting the volume buttons — the relationship between the two depends on a separate setting that people forget they've changed. If the alarm rang but faintly, start with the alarm volume post rather than anything update-specific.
Bluetooth. After a reboot, devices reconnect. If AirPods or a speaker have latched on, your alarm audio may be going somewhere you can't hear it — see where the alarm plays with AirPods connected.
Check 4: Force Restart
If the alarm looks correct and still won't behave, force restart the phone. On current iPhones the sequence is: press and release volume up, press and release volume down, then press and hold the side button until the Apple logo appears. Don't let go at the slider — keep holding.
This is not superstition. Updates occasionally leave background state in an odd condition, and a force restart clears it in a way that a normal power-off sometimes doesn't. It's cheap, it's quick, and it's much less drastic than the steps people jump to instead.
Check 5: Delete the Alarm and Rebuild It
If a specific alarm misbehaves after an update, don't edit it — delete it and make a new one.
The reason is that an alarm carries more state than the screen shows you: a sound reference, a repeat pattern, a snooze setting, a label. If any of that has become stale — a tone that was removed, a schedule that's subtly corrupt — editing the alarm doesn't necessarily clear it. Creating a fresh one does.
Then test it properly. Set it for two minutes from now, put the phone in the exact state it'll be in overnight, walk away, and listen. If the new alarm works and the old one didn't, you had stale state, and you've just fixed it.
When It's Actually a Bug
Real, widespread iOS alarm bugs do happen. Here's how to tell you're in one rather than chasing your own configuration:
- A brand new alarm, created fresh, also fails. Configuration problems usually don't survive a rebuild.
- It survives a force restart.
- Lots of other people are reporting the same specific behaviour in the same window. Check Apple's discussion forums and the usual news sites. A genuine bug generates a lot of simultaneous, identical complaints.
- The behaviour is weird in a way settings can't explain — alarms firing at the wrong time, alarms that ring silently regardless of volume, alarms vanishing from the list.
If you're in that situation: report it to Apple through the Feedback route, keep an eye out for a point release, and in the meantime don't rely on a single alarm. Use a second alarm on another device, or a third-party alarm app that isn't sharing the buggy code path.
What I Do So an Update Can't Cost Me a Morning
Two habits, both cheap.
Never update the night before something important. Update on a Saturday morning, not at 11pm on a Thursday. Then you get a whole day to notice anything odd.
Test your alarm after every major update. Two-minute alarm, phone in its overnight state, listen. It takes less time than reading the release notes.
Beyond that, I stopped depending on the Clock app as my only line of defence. I use Captain Wake, which is built for exactly the kind of stubbornness you want in an alarm: it re-arms through app kills, phone restarts and silent mode, and the volume escalates the longer it's ignored. It has no dismiss swipe — the alarm ends when you complete a mission, which is a photo of a specific object (verified on-device with Apple Vision, so nothing is uploaded), a barcode scan, math, a shake, or a spin. Snooze is capped at a single five-minute round. It's free to download; Premium is around $29.99 a year with a three-day trial, and it's iPhone-only, iOS 17 and up.
And once the technical side is genuinely sorted, there's a second question worth asking, because "the update broke it" is a satisfying story that's often wrong: did the alarm actually fail, or did you turn it off in your sleep and forget? That one is worth being honest about, and I've written about why your brain dismisses alarms without waking you at length. An update makes a convenient culprit. It isn't always the guilty one.
