As the new year was rung in, iPhone alarms remained curiously silent.
Apple has confirmed an iOS bug that left the iPhone without functioning alarms on the first of January. Multiple tests on the iPhone alarm showed that it failed to go off when the digital calendar rolled over from Dec. 31, 2010 to Jan 1, 2011.
Apple spokesperson Natalie Harrison told Macworld that the the bug had been officially recognized, and would fix itself on Jan. 3.
“We’re aware of an issue related to non-repeating alarms set for Jan. 1 or 2,” Harrison said. “Customers can set recurring alarms for those dates and all alarms will work properly beginning Jan. 3.”
However, some iPhone customers in Asia and Europe said they were still experiencing alarm malfunctions as of Jan. 3, according to Reuters. Also, some U.S. customers said on Twitter this morning that their alarms weren’t working.
“This is why I missed the gym this morning,” tweeted Rik Nemanick, a Saint Louis resident.
Apple claims the alarm issue has only affected non-repeating alarms — meaning if your alarm is set to go off at the same time “every Monday,” for example, it should have worked today. However, for those who set a one-time alarm for this morning, some may have experienced the malfunction.
If you’re paranoid about sleeping in late, the quick fix for the issue is to set recurring alarms. To set repeating alarms, launch the Clock app, hit the + sign to create an alarm, then tap Repeat and choose the day(s) you want this alarm to go off regularly.
The alarm code in iOS seems to be pretty buggy. This latest problem follows a bug that caused alarms to sound an hour late when both Europe and the United States flipped over from daylight saving time at the end of the summer.
An unreliable alarm clock is a frivolous bug, but it’s particularly embarrassing for Apple, a company that prides itself for fine details of its products. Here’s hoping that Apple issues a complete rewrite of its clock app whenever it releases the next iPad or iPhone.
iOS bug prevents New Year’s alarms [Macworld]
Photo [Eflon / Flickr]
Updated 10 a.m. PST with reports of people still experiencing the alarm issue, as well as instructions on how to fix the alarm.
See Also: