iPhone Clock Bug Prevents Alarm Triggers after New Year's [Update]
Macworld summarizes findings first reported by Engadget. Apparently a bug in the iPhone clock app prevents non-recurring alarms from properly triggering on New Years day.
I was able to confirm this after a couple of false starts. For the bug to show itself, your iOS device must actually tick over from 11:59 p.m. on December 31, 2010 to 12:00 a.m. on January 1, 2011.
The work around for now is to set up the alarm as a recurring event. 9to5Mac claims that the problem corrects itself after January 3rd. In the meanwhile, be aware if you use your iPhone as your alarm clock.Update: Apple has officially acknowledged the problem:
Apple spokesperson Natalie Harrison confirmed to Macworld that Apple is aware of the problem. "We're aware of an issue related to non repeating alarms set for January 1 or 2," Harrison said. "Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3."
Top Rated Comments
(View all)
Maybe you could give them a pass for messing up daylight savings time - but surely someone at Apple should have known that 1 January was coming!
(yes, I work Saturday)
Thanks Arn!
Perhaps if Apple did a little less patrolling of apps for small infractions (Eg using volume buttons to take pictures) and more testing of the OS, then they might not have lost the mobile space to Android.
First ... Huh?
Second... I'd rather miss an alarm then have my sms messages sent to the wrong person. http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/
No platform is perfect. Bugs exist. Deal with it.
No platform is perfect. Bugs exist. Deal with it.
Yes - but some scenarios can be predicted (for example, 31 December year X changing to 1 January year X+1).
It's pretty sloppy engineering to make bugs like that, and inexcusable QA to ship it with the bug.
Somewhere I saw a JPEG with a picture of a tombstone with "It just works" chiseled into it....
Here's to hoping they can have the problem fixed before 2012.
Having one major clock bug in this day and age is sloppy. Having two is simply unimaginably negligent. Come on, Apple, you're doing so well overall on the big picture, but you have to catch the basic things like this to avoid frustration from your users and ridicule from the tech world and the press.
What might save them from complete embarrassment might be that this hopefully won't affect a lot of people: a lot fewer people have to work on New Year's Day than did the Sunday for the daylight savings/standard time bug. Media outlets aren't going to be doing much real reporting tonight or tomorrow, so this will probably just get buried.
(Kudos to Macrumors btw for posting this on New Year's Eve night; that's dedication.)
Can I call AAPL for some cash refund?:rolleyes:
[ Read All Comments ]
Even as Apple is preparing to open its first Dutch retail store in Amsterdam on March 3, the company is moving closer to expanding its international reach even further as it has updated its Swedish...
Following reports yesterday that Apple would open its first Dutch retail store in Amsterdam on March 3, the company has confirmed that date today with emails to customers and a new dedicated store...
The Charlotte Observer reports that a total of 25 iPhones valued at over $16,000 have been reported stolen from Apple's Northlake Mall retail store in Charlotte, North Carolina. While...
German site iFun.de reports [Google translation] that has it has received information from a source "to be taken seriously" claiming that the iPad 3 will debut there on Friday, March 23.
...
AFP reports that Proview Technology has expressed a willingness to work toward a settlement with Apple in the "iPad" trademark dispute in China, even as the company continues to press forward...
