Another year, another alarm bug in Apple’s iOS. This time it is pertaining to non repeating alarms that your set in 2010 for alerts on January 1 and 2. This is also the first self-healing bug of the year, as the alarm will work properly beginning January 3.
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.
Remember the iOS 4 alarm bug that is affecting European users on Monday as well as Australia, New Zealand users in September? Looks like there is no fixes coming before November 7th, when North America is ending their daylight saving time. Apple has issued a support document advising users to handle the alarm bug manually.
The bug, according to Apple: “In some regions, shortly before or after the daylight saving time (DST) change, repeating alarms created in the Clock app may work incorrectly.”.
To resolve this behavior for existing alarms, set the repeat interval to Never. You will need to reset these alarms for each day you need them. After November 7th, 2010, you can set your alarms to repeat again.
European users who rely on iPhone’s alarm were waking up one hour late today due to a bug in iOS when countries switch back from summer daylight savings time. This is the same iOS bug reported in September when Australia and New Zealand is switching to daylight saving time.
The bug happens when you are using pre-set daily alarm in the Clock app running iOS 4. Using the one-off alarm works as expected though. Apple has acknowledged the issue and is developing a fix. The fix could be in iOS 4.2 which is due sometime in November. Daylight saving time will occur in North America later this week on Nov 7. If Apple doesn’t issue an update in time, the bug will likely affect North American users as well.