Saved by no bell
You're late! Daylight Saving Time means nothing to the iPhone
Bosses, teachers, and coaches all over the world have heard the classic excuse time and time again. It's the oldest one in the book in the hopes of justifying a tardy arrival.
In fact, we're so certain you've used it to unravel yourself from a tangled web of late night partying and lack of next morning prioritization, we'd bet your bottom dollar on it.
And the infamous phrase is: "But...my alarm didn't go off!"
If you are one of the zillions reliant upon your iPhone to run your life — which includes arousing you from slumber in the morning — this would've been your defense for arriving an hour late to work yesterday morning.
And yesterday morning, you would've been forgiven.
Why? 'Cause it wouldn't have been your fault.
If you didn't manually delete and reset the recurring alarms on your iPhone after Sunday's time change — you know, the ones that wake you up for the daily grind — then The Great iPhone Glitch gotcha.
Although you may think the iPhone magically adjusting itself for Daylight Saving Time was enough to keep you and your routine updated, it wasn't enough for your alarm function.
Strangely, Apple is aware (and has been aware) that alarms aren't sounding on schedule with the time change. In fact, the issue first surfaced during Australian Daylight Saving Time, at the start of October. Apple responded by saying it would fix the problem with iOS 4.2.
But with iOS 4.2 currently M.I.A., this particular strain of alarm bug went on to infect both European and U.S. iPhone dependents alike. And there's no panacea in sight.
At least you know it isn't you that sucks at life — it's Apple. And until Apple mans up and fixes the known flaw in its operating system, you have yourself a scapegoat.
Well, you had one, anyway.