Another daylight saving time bug strikes Apple's iOS 7, affects calendar display
Owners of iOS devices running the latest version of Apple's mobile operating system awoke to a display error in iOS 7's calendar app caused by the switch to daylight saving time.
iOS 7's calendar application displays the "current time" line offset by one hour.Thanks to AppleInsider readers Valentijn and Andrea
Several AppleInsider readers have reported the line indicating the current time is displaced by one hour in the calendar app -- for example, at 12:15 p.m., the calendar app draws the "current time" line in the slot for 1:15 p.m., despite displaying the correct time beside the line and in the system notification bar.
The bug reportedly does not affect scheduled alarms or calendar events, the times for which are adjusted properly.
Time zone support is a recurring issue for Apple's software and operating systems. In 2010, iOS 4 contained a bug that did not properly shift alarm schedules when Daylight Savings Time ended, causing some European iPhone owners to miss appointments or wake up late for work, while Australians were woken up early.
In 2011, another iOS 4 bug caused non-recurring alarms to be disabled when clocks ticked over to January 1, 2011. Apple eventually fixed both issues.
iOS 7's calendar application displays the "current time" line offset by one hour.Thanks to AppleInsider readers Valentijn and Andrea
Several AppleInsider readers have reported the line indicating the current time is displaced by one hour in the calendar app -- for example, at 12:15 p.m., the calendar app draws the "current time" line in the slot for 1:15 p.m., despite displaying the correct time beside the line and in the system notification bar.
The bug reportedly does not affect scheduled alarms or calendar events, the times for which are adjusted properly.
Time zone support is a recurring issue for Apple's software and operating systems. In 2010, iOS 4 contained a bug that did not properly shift alarm schedules when Daylight Savings Time ended, causing some European iPhone owners to miss appointments or wake up late for work, while Australians were woken up early.
In 2011, another iOS 4 bug caused non-recurring alarms to be disabled when clocks ticked over to January 1, 2011. Apple eventually fixed both issues.
Comments
Isn't DST next weekend?
DST ended this morning for most of Europe (DST has been coordinated here since 1996 - http://en.wikipedia.org/wiki/Summer_Time_in_Europe) so here in the UK we got an extra hour in bed and are back on GMT.
Just checked my iPhone and it is showing this.... the time by the line is correct at 21:32 but the line is showing around half way between 22:00 and 23:00...
No problems here either – never had a change of hour glitch. Bad luck to those that have a problem.
Just as well the clocks don't change every year then ... or twice ... ah well, gives us all a laugh.
So it seems that many things in this article seem to be messed up.
apparently it dates back to farmers milking cows or something.
That's completely opposite. DST is because people stay awake at night more than they do in the day, so you shift the clock so you get more daylight. People stay up till say midnight, which is sunset + ~6 hours. You don't wake up at sunrise - 6 hours = ~1 AM.
Farmers dislike DST because their day is set by the sun, not the clock. I guess people like to bash farmers as hicks when they don't know what they're talking about.
But no, as usual they miss it. Come on Apple, considering all that you manage to achieve surely this is not rocket science to you?!?!?!
Here in UK the bug has hit
Calendar currently it's 10:45pm, the line shows after the 11pm line , not before 11pm
Suggestion to Apple - it would be nice if Apple noted (in parenthasis) that this was UTM time.
DST dates back to WWII when it was felt that by moving the hour would help save electrical energy, which it did. Two funny stories relating to DST:
The summer it was first implemented there was a hot dry spell in the USA. A farmer wrote in to the local newspaper complaining about DST burning up his corn crop.
The second funny story concerns Moscow Russia. During the 1950s Central Planning forgot to tell those who keep official time to end DST one Fall. With Stalin in control, no one dared question it. The next spring Central Planning told everyone to set their clocks ahead and again forgot to end DST that fall again. It wasn't until the fall of the USSR that people got brave enough to question why they were living two hours earlier than they should. It was not until nearly 50 years after the fact that Moscow got back on the right time.
Anyone want my DST rant? I hate DST more than a few of the things I’ve hated here.
Seriously, drop all this nonsense. Imagine you’re an alien, looking down on the planet. What would you think?
“So… twice a year you guys just pretend it’s a different time? Why, again, should we consider you sapient and therefore immune from becoming a slave race?”
Anyone want my DST rant? I hate DST more than a few of the things I’ve hated here.
Seriously, drop all this nonsense. Imagine you’re an alien, looking down on the planet. What would you think?
“So… twice a year you guys just pretend it’s a different time? Why, again, should we consider you sapient and therefore immune from becoming a slave race?”
Can't wait to hear your Leap Year rant...
Can't wait to hear your Leap Year rant...
Oh, that wasn’t all of it. Just a taste.
Interestingly enough, I like leap years. Sort of wish my birthday was February 29.