Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Says 'Do Not Disturb' Bug to Resolve Itself on Monday, January 7th
- Thread starter MacRumors
- Start date
- Sort by reaction score
As a pretty big Apple customer, I find this a slap in the face. I missed a number of calls/text this morning due the bug. Having to just wait a week is completely unacceptable by someone like Apple.
Clearly their new leadership thinks we'll keep buying regardless of the quality.
Clearly their new leadership thinks we'll keep buying regardless of the quality.
Clear-cut case of user error
It's always something.
----------
You were obviously holding her wrong.
Bug is Indicative of a Quality Decline ....
Especially after the last New Years Eve bugs, how incompetent does a QA department have to be to NOT set the phone to 1/1 and test all time dependent functionality?
This is a disconcerting tick mark on a trend in Apple which seems to point to declining quality overall.
Especially after the last New Years Eve bugs, how incompetent does a QA department have to be to NOT set the phone to 1/1 and test all time dependent functionality?
This is a disconcerting tick mark on a trend in Apple which seems to point to declining quality overall.
Of last year, this is the second time in a row a crucial time based feature over New Years has failed on iOS (last year alarms became mysteriously disengaged/hindered after the new year).
Last edited:
Just wanted to point out that you called something "over-played" and then said "Captain obvious".
Says a guy who is clearly not a programmer, much less a competent one. I love watching people fall into the old chestnut of, "I don't understand how something works, so it must be so simple an idiot can do it." (Making it all the more laughable that they're so willing to broadcast that they don't have the slightest clue how to do it.)
As a programmer, I'll state for the record, due to the way dates are usually stored in memory, as a floating point value with the date to the left of the decimal, and the fraction of the day (aka: time) to the right, and the fact that this functionality doesn't actually care *which* dates are involved, there *should* be no difference between the transition from Dec 31 to Jan 1 and the transition between any other two random days. Now, obviously, it *did* have a difference, but it's probably not because of anything special about the days involved.
Then again, while this feature is easy to conceptualize, it's quite a bit more involved to actually implement. (As is true of *many* features.)
You want to rag on someone for a date-bug that actually deserves it? Look into the Excel leap-year bug. It's been known about, and unfixed for better than a decade now, and it never will be fixed. Worse, they codified the *incorrect* leap year calculation into the XSLX format standard "for backward compatibility purposes" rather than fixing it. Still worse, it was intentionally introduced in Excel 2000 (for reasons to do with grabbing market share from the dying Lotus 1-2-3) after being handled correction in all prior versions of Excel.
That's a bug worth bitching about. This one? It's annoying. That one? You'd be amazed how many places use spreadsheets to track all sorts of things that actually impact people directly. (One of the many things that leave us programmers thumping our head on our desk when someone asks us to 'fix' the spreadsheet that we had no hand in creating, don't know what' it's *supposed* to be doing, and nobody can tell us because the guy who first created it left the company 3 years ago.)
To quote Lois CK when the newly intodroduced wifi stopped working on the plane.....
" 'This is bull ****.' How quickly the world owed him something he didn't even know existed 10 minutes ago."
Seriously people. This function was only introduced a few months ago. It's not like you've been living you're entire lives with this feature and it's all of the sudden been taken away from you. It's still there. You just have to flip the switch manually for 5 more days. Apple is not doomed, your life will not end. It will fix itself faster than a patch will be put out. Relax. Go about your day the same way you did before DND was even introduced.
" 'This is bull ****.' How quickly the world owed him something he didn't even know existed 10 minutes ago."
Seriously people. This function was only introduced a few months ago. It's not like you've been living you're entire lives with this feature and it's all of the sudden been taken away from you. It's still there. You just have to flip the switch manually for 5 more days. Apple is not doomed, your life will not end. It will fix itself faster than a patch will be put out. Relax. Go about your day the same way you did before DND was even introduced.
Last edited:
Why don't you go move to a third world country if you are such a wonderful lover of the undeveloped world.
Yes, there's 'always' a set of updates/fixes/patches/etc. in the works. No, there's *NOT* always a set of updates/fixes/patches/etc. which have been sent through the full QA process to ensure that no new issues have been created as a result of those updates/fixes/patches/etc.
You can't push out an update until the change set has been frozen, and everything has been tested. That process, especially for something as complex as an OS, and it's associated utility apps, is going to take multiple *days*, if not a couple weeks (depending on how many of those updates/fixes/patches/etc. are included in the release).
So, given that, when the bug was found, it was quickly discovered to resolve itself on the 7th (5 days from now). Given that it would take at *least* that long to create the fix, bundle the new version for testing, and push it through testing to be released, how on earth does it make sense to bother?
It's a critical issue if you're going to drive across the state tomorrow, and your car is going to run out of gas in just 10 miles, right? So you should do something about it *NOW*. But in this case, you're already at your destination, and you were already planning on stopping at the gas station 5 miles down the road when you left anyway.
According to the logic of some of the people here, you absolutely positively *MUST* get back in the car and go fill the tank *NOW*, even though it has absolutely no impact on the end result. (In both cases, the car's tank gets filled before it's actually empty, and you start your trip the next day with essentially a full tank.)
Additionally, forcing a rushed patch schedule, with limited time for testing, adds the extra danger of a worse bug being introduced as a result of the 'fix' that was released. So that makes it more akin to insisting that you *must* go fill the gas tank *now*, even though it's a bit icy out, and the road crews won't be through for a couple hours. (IOW: It's *less* dangerous to wait and work according to your normal plan, because the end result is still the same.)
I was more surprised that it was a "fundamental problem" even though people were only "inconvenienced by it". It's a problem, sure. But if you're only inconvenienced by the problem, it sure as heck isn't a fundamental one.
The second year in a row where "this exact" bug occurred? Wasn't DND new with iOS 6, released (much) less than a year ago? Or are you confusing "this exact" bug with a similar (but different) one which occurred in Jan 2011? You do also realize that user-set alarms still function normally even with DND activated, right? DND just stops things like email alerts and the like from making noise.
Chill with the hyperbole
Y'all are being a bunch of whiny brats. Knock it off. Jesus. Yes, it's an annoying bug (for some).
We've enjoyed our iPhones without this feature for over 5 years, and now your life depends on it? Give me a break.
Kudos to Apple for acting like the parent in this situation. They could spend loads of time and money to race around to all the different stores and get the kids their toys and candy, but instead, they say "wait a few days, you'll be fine".
And you will.
Y'all are being a bunch of whiny brats. Knock it off. Jesus. Yes, it's an annoying bug (for some).
We've enjoyed our iPhones without this feature for over 5 years, and now your life depends on it? Give me a break.
Kudos to Apple for acting like the parent in this situation. They could spend loads of time and money to race around to all the different stores and get the kids their toys and candy, but instead, they say "wait a few days, you'll be fine".
And you will.
Yes you're right there are many of people encounter that issue however apple really made a good job on fixing it and it was awesome.
Well, given that android's calendar missed out the entire month of december until it was fixed in an update, i'd say this bug is small fry.
Samsung/google would be standing in a nice big glass house throwing stones...
After Apple fired their software manager, I expect to see less of this nonsense going forward...
You are big customer? Do you eat a lot or do you mean you buy a lot of consumer products from Apple?
This thread is hilarious.
How many bugs has Windows survived?
Lol at anyone who had their life "ruined" by this insignificant bug.
You want to see bugs?
Call Android.
How many bugs has Windows survived?
Lol at anyone who had their life "ruined" by this insignificant bug.
You want to see bugs?
Call Android.