I guess you are one of those programmers who has never made a mistake. You should probably go and work for Apple to prevent this from ever happening again. And I don't see what the problem is with their attitude. If you look at the turnaround time for Google's December bug, it was filed on November 14, the patch went in on November 19, and OTA started rolling out on November 27. If Apple was to have similar timing, it could say that an update would be out in 2 weeks, or they could say it will resolve itself in 5 days. Which is better?
Heck, my wife got a bug shortly after we got married. We had to wait 9 months before it got automatically resolved.
So what happens next year?
And what about other issues? Should we turn our phone off for several days?
Unacceptable Apple!
This is really annoying, especially since I had also set it to reject calls except VIP numbers when on Do Not Disturb. Normally a great feature to guarantee a good night's sleep.
It took me until yesterday evening to notice it hadn't switched off after the night (when I read about the bug here) so I could have lost some calls.
So the bug didn't occur on my device yesterday morning (1/1/13), but then it did this morning (1/2/13). Is that consistent with what others are experiencing?
So what happens next year?
And what about other issues? Should we turn our phone off for several days?
Unacceptable Apple!
People, are you all idiots? You don't think they will release an update before the next ****ing new year? Also, how could they fix this problem so quickly after it happens when it will fix itself so soon? They would have to push an update way too quickly. Apple has bugs, EVERYONE HAS BUGS. What the hell is so bad about them saying the truth to us?
Poor cry-baby might have missed a call. Anyone that needs to use this feature to screen calls likely doesn't get any that are of much importance anyway.
well i guess I won't get any sleep from now until the 7th. God I love waking up to emails that jeans are 20% off
moaning about a software bug that is taking a whole 7 days to fix? not bad if you ask me especially for a non critical bug.
Given that they're coming off a holiday, and that they won't be efficient in patch release (as always), it's unlikely they'd deploy anything before then anyways.
Someone made an oopsie in the code but fortunately it only hits this week; next years solution will be baked into 6.1.
Bawww i must manually enable or disable a feature for some days UNACCEPTABLE I PAID FOR THIS FEATURE
No joke. What is the deal with Apple that they come off with the "You're holding it wrong" mentality on every issue these days. NO Accountability! Apple has gotten too big for their own good. Rediculous!!!
----------
You're saying Apple couldn't patch that in about 2 seconds? Talk about idiots