



Personally, I make use of the Do Not Disturb feature that was added in the release of iOS 6. Now my phone and iPad both know at midnight to mute all notifications and to silence my ringer. There will be no interrupting my sleep!
But, on New Year’s Day I noticed both my iOS devices were being suspiciously quiet. In fact I knew I had received some tweets but never heard the distinctive sound of a Tweetbot notification. When I checked my phone and iPad I noticed that the Do Not Disturb logo was still showing on screen. Luckily it was easy enough to turn the feature off and once again I was receiving all of my notifications.
I did notice that my notifications kept coming one even when Do Not Disturb should have triggered. After digging around on the internet a little bit I saw I wasn’t the only person with this issue. Today the folks over in Cupertino acknowledged that there is in fact a bug affecting Do Not Disturb:
“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.”
So lucky for us, it seems the error will fix itself and not require an new software update. Continuing good news since iOS updates are notoriously slow to roll out. Its also interesting to note that this isn’t the first time Apple has had issues pop up with the beginning of a New Year. Last year scheduled alarms were disabled when the year rolled over to 2012. So, I guess the question now is, what iOS error will there be when 2014 rolls around? Any guesses?
That’s funny – just last night I was showing my wife the feature. I’m glad I didn’t set a schedule or my face woulda been red :D
Haha it got me!
So did it end up working? I’m too lazy to check. :P
It did work. Found out its because iOS is not based on the Gregorian calendar in the background and that caused this bug.