14 DAY TRIAL // Spanning a year worth of Apple software updates and headaches reported by iOS customers worldwide, the alarm clock bug plaguing Apple’s mobile operating system has emerged yet again, courtesy of the time change (daylight savings) this past weekend.
Apple has failed to neutralize an error causing users’ recurring alarm clocks to go off one hour late, or not at all, despite the recent release of iOS 4.3.1.
Released March 25th, iOS 4.3 fixes an occasional graphics glitch on iPod touch (4th generation), resolves bugs related to activating and connecting to some cellular networks, and issues authenticating with some enterprise web services, as well as image flicker when using Apple Digital AV Adapter with some TVs.
The changelog said nothing about fixing battery life issues for some users, though customers have indeed reported an improvement in their iOS devices’ power management.
The same thing cannot be said about the ever-present alarm clock bug which strikes every time daylight savings kicks in, regardless of the user’s location (time zone).
The circumstances in which the bug kicks in have long been determined (recurring alarms), yet Apple still hasn’t properly addressed it.
We don’t expect the company to issue iOS 4.3.2 just for this bug, although it would be a nice touch, considering how many times people failed to get to work on time because of Apple’s mistake.
However, it is still unclear whether these reports are coming from users who’ve upgraded to iOS 4.3 or iOS 4.3.1.
We trust Apple would have documented the fix in the release notes.
As such, we ask you, the readers, to write down your experience in the comments.
Those who’ve been affected by the bug are encouraged to post their iOS version and type of alarm set (recurring, or non-recurring), to better determine who’s had troubles, and who hasn’t.