Apple has released an acknowledgement that the sporadic issues with Do Not Disturb are legitimate and are being addressed. On the Apple Support site yesterday, Apple posted article TS4510 which outlines the problem of Do Not Disturb mode staying on even after the scheduled time for it end has passed. The resolution to the issue is interesting:
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.
What makes this interesting is the “resume normal functionality” statement. Does this mean that whatever this bug is, likely algorithm related, runs its course on 7 January and things return to normal? Or does it mean that we can expect to see a hot patch of some sort for iOS 6 to resolve the issue on 7 January? It really doesn’t matter but the blogosphere is alight with the idea that this will be a software patch – I’m not convinced yet.
A deeper question – and I’d like to hear your thoughts – is why does Apple have a difficult time with the calendar rolling to a new year and Daylight Savings Time? They have been plagued with issues related to one or the other or both in iOS 4, iOS 5 and now iOS 6.
You can read TS4510 here and remember to turn off DND manually between now and the 7th.
There have been some reports via Twitter and a few other Apple centric sites this morning about a bug impacting scheduled Do Not Disturb and the rolling of the calendar to 2013. I can report that I’ve seen the bug on my iPad (3rd Generation) but my Scheduled DND turned off as normal on my iPhone 5.
Take a look at this screen capture I made this morning from my iPad. Note the scheduled DND is still enabled even though the time is past the scheduled end time of 08:00. I had to manually turn of Do Not Disturb instead of it disabling itself automatically as it did throughout 2012.
The interesting thing is that I did not see this problem on my iPhone 5. The Do Not Disturb is set up exactly the same way on it as it is on my iPad and it disabled itself as normal this morning. Others have reported this being a problem on their iPhone 4S and 5 so it doesn’t seem to be isolated to just the iPad. In other words, it could be the worst kind of bug: No method to the madness.
I will update this post as I gather more information or if Apple releases any statement regarding this maybe-or-maybe not bug.