Apple: Wait for 'Do Not Disturb' bug to resolve itself

Yesterday, iOS 6 users found out that the new year introduced a minor bug in Apple's mobile operating system. The 'Do Not Disturb' feature, which lets users silence calls and alerts at scheduled times, will not turn off automatically. A quick workaround is to manually turn the feature on and off.

So what's Apple's solution for this problem? Wait until it resolves itself. The company published a support article on their website stating normal functionality will be resumed after January 7:

Symptoms 
After January 1st, 2013, Do Not Disturb mode stays on past its scheduled end time.

Resolution
Do Not Disturb scheduling feature will resume normal functionality after January 7, 2013. Before this date, you should manually turn the Do Not Disturb feature on or off. To turn off the scheduling feature, tap Settings > Notifications > Do Not Disturb and switch Scheduled to Off.

It's understandable that the developers at Apple chose to just wait, rather than to develop and test and a new bug fix release of iOS after they found out the situation resolves automatically in five days. Still, users are likely not amused by the bug and Apple's solution.

Source: Macrumors | Image via Macrumors

Report a problem with article
Previous Story

James Bond Activision games removed from Steam

Next Story

US Department of Defense to start using Windows 8, buys $617 million worth of Microsoft licenses

54 Comments

Commenting is disabled on this article.

Gotta love these annual date and time bugs that Apple seem to get year after year. This is like the third year in a row that they have had issues. =D

Crap response to an obvious big flaw in their software. Whilst I can't see myself looking at Android again the crap Apple have churned out since the iPhone 4 are making me think I need to go try WP8. If the Windows Store had the same quality apps the App Store does I wouldn't think twice about it.

some of these comments are ridiculous...
"it's money consuming..."
yeah, that shouldn't be an issue... especially for apple at this point in time.

"it's physically impossible to release an update in 5 days"
no, it's not. companies do it all the time, for e.g. when a major security bug is found. if they wanted to, they could release a patch for this in one day. it's being lazy.

wookietv said,
some of these comments are ridiculous...
"it's money consuming..."
yeah, that shouldn't be an issue... especially for apple at this point in time.

"it's physically impossible to release an update in 5 days"
no, it's not. companies do it all the time, for e.g. when a major security bug is found. if they wanted to, they could release a patch for this in one day. it's being lazy.

This isn't a serious bug, it's a minor inconvenience with two solutions; either wait or turn it off and on again. It's not worth their time or money.

Sotto_Zero said,
Ok. Wait a minute. Apple is having an Y2K bug 13 years after the year 2,000 and everyone thinks it is perfectly OK?

Not everyone, just the most "devoted" apple fans

Sotto_Zero said,
Ok. Wait a minute. Apple is having an Y2K bug 13 years after the year 2,000 and everyone thinks it is perfectly OK?

Nobody said that it's okay, just that it would be pointless for Apple to create a fix, test and then deploy it when the bug rights itself after five days. By the time they've done this it will have fixed itself, rendering the update pointless.

They should address the bug so it doesn't happen next year but they can include that fix in a more meaningful software update rather than specifically to address this issue.

It seems like every time Apple does something like this that gets poorly re-used in bad jokes, they do something else to create another template for a series of more overused bad jokes.

About as amused as the "hold it the other way" or "Youtube does HD", lets not get into the other time-keeping problems iOS has had over the past.

I don't feel like this is really a big issue, you manually turn it off for the next 5 days and go on with your life. It should be patched when they release their next update. The bigger issue to me is their attitude about problems like this when they come up.

I agree that this is a non-issue. Anyone who thinks you can develop, test, and deploy a fix at this scale in a shorter time has zero experience with software development and can just choke on their opinion.

Joshie said,
I agree that this is a non-issue. Anyone who thinks you can develop, test, and deploy a fix at this scale in a shorter time has zero experience with software development and can just choke on their opinion.

Why do rational comments appear only when Apple screws up? If any other tech companies does something this stupid they'll be long flamed to a crisp.

I'm not sure which is worse - Scientology or Apple.

resol612 said,

Why do rational comments appear only when Apple screws up? If any other tech companies does something this stupid they'll be long flamed to a crisp.

I'm not sure which is worse - Scientology or Apple.


I'm not every commenter, and I don't speak for the comments posted by others, nor they for me.

In all cases, people who form opinions based on unrealistic expectations can choke on those opinions. People who form opinions based on rushed conclusions can choke on them. People who form opinions based on high-spin hyperbole from just one side of an issue can choke on them.

Opinions are addictive, and people are loathe to take responsibility for them. They desperately reach out for something to scream about and take extreme offense when their unsubstantiated perspective is met with the slightest challenge.

They can all choke on them. Equally.

Joshie said,

I'm not every commenter, and I don't speak for the comments posted by others, nor they for me.

In all cases, people who form opinions based on unrealistic expectations can choke on those opinions. People who form opinions based on rushed conclusions can choke on them. People who form opinions based on high-spin hyperbole from just one side of an issue can choke on them.

Opinions are addictive, and people are loathe to take responsibility for them. They desperately reach out for something to scream about and take extreme offense when their unsubstantiated perspective is met with the slightest challenge.

They can all choke on them. Equally.

Funny, you mention choking in two back to back comments. Do you routinely choke on something long-ish with a tapering tip on one side?

javagreen said,

Funny, you mention choking in two back to back comments. Do you routinely choke on something long-ish with a tapering tip on one side?


Not at all. My gag reflex is well trained.

JessJess said,
Our washing machine is working fine too.

Your brain seems to function perfectly fine too. What happened? Apple flavoured Kool-aid machine no dispense?

apple have had problems with DST time bug and all sorts of timer, alarm and other issues over the years, do they not bother testing? Google forgot the month of december in android 4.2 final so clearly they didn't do much testing either.

I'm not an apple fan, but I find this to be pointless bashing - not even front page worthy.
Apple didn't say they wont fix it. Its just that the fix (which is probably already fixed by their development team) and distribution of this minor fix within a week is pointless. It'll probably roll in their next iOS update.

At least Apple acknowledged the bug and found that it will resolve itself. Release testing takes a very long time and it would be physically impossible for them to release a fix within the next few days. It's not an earth-shattering bug, so people can deal with it for the rest of the week.

Yep, and when the Zune had a bug that was triggered on Jan 1 of a leap year causing Zune devices to freeze for a few hours, well there was hell to pay! How dare Microsoft release a faulty product? Why are they not fixing it now? Microsoft purposely built this in!

But every year there is a new bug with an Apple device telling time - eh, just wait a week, you can deal with it.

Oh, and those comments I posted about the Zune above can be found in here:
http://www.neowin.net/news/mai...ling-due-to-software-glitch

I followed the link that you posted thinking that I would see a post from Astra.Xtreme flipping tables over the Zune bug, but I didn't find anything. I even Ctrl+f. Did I miss something? I was under the impression that you were going to expose Astra for being a hypocrite. I was let down.

nohone said,
a bug that was triggered on Jan 1 of a leap year causing Zune devices to freeze for a few hours

The bold part. It's important.

omgben said,
I followed the link that you posted thinking that I would see a post from Astra.Xtreme flipping tables over the Zune bug, but I didn't find anything. I even Ctrl+f. Did I miss something? I was under the impression that you were going to expose Astra for being a hypocrite. I was let down.

I didn't say that Astra made those comments. The point is that he is saying it is no big deal when it happens for a week, but when other devices have an issue for a few hours, the Apple fanboys have a field-day attacking. Ok to attack when it is not Apple, but when Apple does have a problem, move along, nothing to see here, stop being so mean to Apple.

JessJess said,

The bold part. It's important.

Being that we hear over and over how relatively few people used Zune and how many people use iOS, the supposed quality of Apple products over other devices thus justifying the higher price, and that Apple has this same problem over and over, shouldn't we expect better?

JessJess said,

The bold part. It's important.

Also, the problem with Zune was found to be in a driver for a chip provided by a 3rd party. When Apple has a problem with a video card overheating, a bad screen, a bad HDD, a bad touch pad, people immediately jump to Apple's defense, that it is not Apple's responsibility to test the cards, it is up to the 3rd party to provide Apple with working components. So when the products are provided to device makers other than Apple, why shouldn't those device makers be clear of blame? Not saying they should, Microsoft should have tested the 3rd party code, just as Apple should test the graphics cards, screens, touch pads, etc. But many people are quick to blame one company, and quick to defend another when the same problem happens.

nohone said,

Also, the problem with Zune was found to be in a driver for a chip provided by a 3rd party. When Apple has a problem with a video card overheating, a bad screen, a bad HDD, a bad touch pad, people immediately jump to Apple's defense, that it is not Apple's responsibility to test the cards, it is up to the 3rd party to provide Apple with working components. So when the products are provided to device makers other than Apple, why shouldn't those device makers be clear of blame? Not saying they should, Microsoft should have tested the 3rd party code, just as Apple should test the graphics cards, screens, touch pads, etc. But many people are quick to blame one company, and quick to defend another when the same problem happens.

You've just discovered the smokescreen apple zealot theory where any and all errors and blatant disregard by Apple to it's user base should be seen and accepted as completely normal.

Any attempts to highlight those will make you part of the "resistance" and must be destroyed.


javagreen said,

You've just discovered the smokescreen apple zealot theory where any and all errors and blatant disregard by Apple to it's user base should be seen and accepted as completely normal.

Any attempts to highlight those will make you part of the "resistance" and must be destroyed.


I know this very well, but I should say that this is by the biggest of Apple fanboys. There are a number of Apple fans around here that are willing to accept that Apple is not perfect, and make mistakes. I have a lot of respect for people like Glassed who is an Apple fan, but not a fanboy. I have been accused of being a Microsoft fanboy, for example my preference of the music app built into Win8 over iTunes. But I will prefer an app that is slow and awkward to use over an app that deletes data - but I would like it if the Win8 app was not slow and awkward.

nohone said,

Also, the problem with Zune was found to be in a driver for a chip provided by a 3rd party.

Oh boy the 3rd party excuse again.

I guess the reason why my plug and play cable was not charging my battery yesterday was because of a 3rd party company too ...

LaP said,

Oh boy the 3rd party excuse again.

I guess the reason why my plug and play cable was not charging my battery yesterday was because of a 3rd party company too ...

And obviously you didn't read my entire comment, where I made the argument it is not an excuse. My comment is still up there in its entirety, go ahead and read it, I will wait...

I think the alarms went off even if one wasn't set and it couldn't be stopped. Then there's the DST issues they've had for the last couple of years?

In the age of modern smartphone devices, you'd think Apple/Google/etc. would have no problems with date and time operations...it seems more prominent in iOS

Im not. I curse the times i have to work with DateTime objects. Not becuase they are necessarily hard, but because they are central to syncing data, and one little mistake about a timezone's offeset, or forgetting to properly format for a region can raise so much havok.

yes but the bug was corrected easily
was only with the birthday custom field and was not essential to any function of the OS

There's no way they could test and roll out an update quicker than it'll resolve itself, and it'd be a bit of a waste of resources if they did. It's most likely caused by using yyyy and YYYY in different parts of the same calculation when using NSDateFormatter. Simple problem which can easily slip through unit testing, and I imagine it'll be fixed in the next minor update (well in time for new year).

I don't know about Apple, but we at least try to use a global date format string to help prevent issues like this