Apple Says 'Do Not Disturb' Bug to Resolve Itself on Monday, January 7th

First world problems here...

So what happens next year?

And what about other issues? Should we turn our phone off for several days?

Unacceptable Apple!

So true. I'm not usually one to cry "unacceptable" but this truly is. "Don't use it for a week and it will resolve itself" is just a crap answer for a third rate company, not acceptable for the "it just works" company.

The bug is so bad, that even the act of adjusting the on time for the feature turns it on instantly.

So, what else isn't working that Apple knows about and doesn't give a damn about? Privacy features? Security features?

They are basically telling millions of customers that they don't give a damn.

Google or Samsung need an add making fun on this one...

So just ignore the problem and it will go away eventually.

"You're holding it wrong."

this is so absolutely mind-boggling. it will resolve itself on the 7th, so just relax? really? what a message to send to customers, i'm really floored.

I view this more as a feature than a bug.

So what happens next year?

And what about other issues? Should we turn our phone off for several days?

Unacceptable Apple!

As a programmer, I'd be interested to learn why it will resolve itself on January 7th. Is it because it's the first Monday of the year? That would line up with last year's bug fixing itself on January 2nd.

So true. I'm not usually one to cry "unacceptable" but this truly is. "Don't use it for a week and it will resolve itself" is just a crap answer for a third rate company, not acceptable for the "it just works" company.

The bug is so bad, that even the act of adjusting the on time for the feature turns it on instantly.

So, what else isn't working that Apple knows about and doesn't give a damn about? Privacy features? Security features?

They are basically telling millions of customers that they don't give a damn.

Google or Samsung need an add making fun on this one...

Way to overblow an insignificant little problem.

As a programmer, I'd like to know the exact reason to wait a week for this to correct itself, and why this wasn't caught earlier. 2 years in a row with these types of bugs. Whenever I test dates while coding, I will reset the date of the device back to 11:59 on December 31st over and over again to test things. Maybe the bug doesn't crop up then?

It's a problem, but nothing anywhere close to the 'Sudden Death' Samsung Galaxy S3 problem, which Samsung is giving no clue as to when they will fix the bug except for saying 'they want to bring out an update as soon as possible'.

Heck, my wife got a bug shortly after we got married. We had to wait 9 months before it got automatically resolved.