Today is Daylight Savings Time in the United States, which is always a hazardous time of year for owners of iOS devices. Why? Because try as Apple might they just can’t seem to release a version of iOS that does not have that are triggered by the switch to Daylight Savings Time.
No joke: Apple has had bugs come up in iOS after the switch to Daylight Savings Time in 2010, 2011, and 2012, while 2013 saw a similar New Year’s Bug screw up Do Not Disturb for device owners. Now here we are in 2014. Does iOS 7 contain a Daylight Savings Time bug?
It does! If you open Calendar on your iOS 7 device, you will notice that while the time of your operating system is set correctly, the line marking the time in Calendar is an hour old. It’s a minor bug, but hey, how would we remember Daylight Savings Time at all if our iOS devices didn’t go wonky once a year because of it?
Thanks: Shane C!
John Brownlee is a writer for Fast Company, and a contributing writer here at CoM. He has also written for Wired, Playboy, Boing Boing, Popular Mechanics, VentureBeat, and Gizmodo. He lives in Boston with his wife and two parakeets. You can follow him here on Twitter.
29 responses to “Yep, There’s A Daylight Savings Time Bug In iOS 7.0.6”
I just checked Calendar on my iPhone running 7.0.6, and the the line marking the time in Calendar is accurate.
I’m running 7.0.6 and the line is wrong, but the time is correct…
Now that I look again, I see that the line is wrong, but the time is correct.
My Calenda line and time are now correct.
Hmmm…mine is correct. Maybe it’s just some people.
mine is correct too
I did not have an issue either… Out of ideas for real stories?
Mine is inaccurate. Shows the correct time, but the line is in the wrong place…Just because yours is correct, doesn’t make this made up.
mine is correct
7.0.6 iPhone 5…my line is NOT correct. Exactly how the picture in the article shows it.
The time is correct, but my alarm didn’t go off this morning. I worked for years on the Y2K problem, and I can only shake my head at the ineptitude on display here. Good thing there were no iPhones in 1999!
mines good…..that all you got?
Wow, a lot of stupid people here. If you are running 7.0.6 and you are in a DST time zone, then your calendar is WRONG. Just like dcj001 who initially thought it was fine because he didn’t look closely enough, the app is wrong. Look harder.
Umm no. I do live in DST zone and my phony time, calendar time and time line are ALL correct. What’s “stupid” is making a statement as fact when you have no possible way of knowing if what you are stating is accurate. You know what they say about ASSumptions.
I mostly agree with you, but must point out that you are making an assumption that we all “know what they say about assumptions.” :-)
See http://xkcd.com/1339/
No as a matter of fact I do live in DST zone and my phone time, calendar time and calendar time line are ALL CORRECT! What’s “stupid” is making ASSumptions and stating as fact when you have no possible way of knowing what others devices are doing!
No, you’re an idiot and you’re WRONG, which makes you one of the stupid people. I’ll put it in terms you can understand. “Ya ain’t got no brains in yer goldurn head!” Mine is correct and it was all day yesterday too.
*Daylight Saving Time
–> No second “s” in the word “Saving”
“Because try as Apple might they just can’t seem…”
Man, John just LOVES to rag on Apple any way he can. It’s occurred to me before that he’s being paid by Apple’s competition. Now, I truly believe it. Otherwise, is it really necessary to couch these middling problems in such dire words? Poor, if not unnecessary reporting.
I just checked my calendar ios 7.0.6 and it is also correct.. I’m not sure if this guy writer’s credibility is to be believed.
I don’t use the Apple calendar and it’s correct. Maybe just an individual app issue?
mines accurate, way to create an issue when there isnt one
“Why? Because try as Apple might they just can’t seem to release a version of iOS that does not have that are triggered by the switch to Daylight Savings Time.”
Aaaaah… now I understand why.
It has corrected itself.
For everyone who thinks they didn’t have a problem, they likely saw the correct time but didn’t double check the location of the red line – the location of the red line was the bug – and it was wrong.
Im in the UK but my iPhone had a freak out this morning. It told me it was 10:35am when it was actually 9:35am. When the time reached 10am it went back to normal.
Mine’s fine, too.
“…iOS that does not have that are triggered by…”
Learn to proofread and edit before your post “official” “stories”.
My phone shows the line in the correct location based on the time.
It’s Daylight Saving Time not “Savings”. Leave off that last “s” for savings :-)