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

Discussion in ' News Discussion' started by MacRumors, Jan 2, 2013.

  1. macrumors bot


    Apr 12, 2001

    Some users discovered that the scheduling portion of the "Do Not Disturb" feature in iOS 6 failed to work after New Year's Eve. The scheduling would turn itself on as scheduled, but would fail to turn itself off again.

    Apple reports in a support article that Do Not Disturb scheduling will begin working properly again after January 7, 2013.

    Article Link: Apple Says 'Do Not Disturb' Bug to Resolve Itself on Monday, January 7th
  2. macrumors 603


    Jan 8, 2009
    None of my iOS 6.1 beta devices suffered from this issue, while my 6.0.x devices did. I wonder if this is an indication that Apple plans on the 6.1 release to be around the 7th.
  3. macrumors member

    Apr 13, 2008
  4. macrumors 68020

    May 20, 2011
    So what happens next year?

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

    Unacceptable Apple!
  5. macrumors 6502

    Sep 21, 2008
    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.
  6. macrumors 6502a

    Jan 24, 2011
    So just ignore the problem and it will go away eventually.
  7. macrumors 6502

    Oct 1, 2007
    Nah. It just means for some reason the bug effects the first week of the year.
  8. macrumors member

    Feb 29, 2012

    Mine doesn't even switch on as scheduled.
  9. macrumors 6502


    Sep 17, 2003
  10. macrumors regular

    Sep 2, 2009
    No, the bug corrects itself on the first Sunday of each year. This bug will be squashed in the next update though, so I wouldn't expect to see this again next year.
  11. macrumors member

    Sep 13, 2012
    Bad Programmers = Bad Programs. WOW, what a solution.
  12. macrumors regular

    Apr 10, 2009
    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...
  13. macrumors G5


    Nov 14, 2011
  14. macrumors 6502

    Jul 7, 2012
    Elsewhere, USA
    The first day I turned mine off and then on again, it worked. This morning, not so much - had to turn it completely off and leave it off.

    Does the world end on Jan 6 and this is just Apple's way of not dealing with it?
  15. macrumors regular

    Jan 23, 2003
    down on the upside

    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.
  16. macrumors G4

    Oct 23, 2010
    That's not what they said. You can manually turn it on or off. My guess is that by the time they got a patch out, it would already be 1/7/13. I noticed the issue on mine yesterday, but after manually turning it off yesterday, it seems to have resumed normal functions (meaning it turns on and off as normally). The risk in rushing out a patch is that they inadvertently screw up something else. This isn't affecting everyone who uses DND.
  17. macrumors 603


    Jan 8, 2009
    Ah, makes sense. Thanks :)


    Seems to be, which surprised me, but, ah well
  18. macrumors 68000


    Mar 28, 2008
    Manchester UK
    Christ, can't they just fix the dam BUG in a mini update?
  19. macrumors 68020

    Jul 8, 2006
    So this means that people can disturb me all they want until Monday, well I guess that's just fine and dandy!
  20. macrumors 6502a

    Jun 23, 2007
    More bad publicity. They just can't catch a break.

    Maybe hire a few more testers since surely this was an obvious thing to test for.
  21. macrumors newbie

    Feb 13, 2008
  22. macrumors 6502a


    Apr 19, 2004
    New Jersey
    My iPhone 5 which is running the beta of 6.1 is experiencing the issue. My iPad Mini which is running 6.0.2 seems uneffected.

    Dont think its 6.0.x specific.
  23. macrumors regular

    Nov 21, 2009
    Nice try, but not applicable in this case. There's not even a hint that Apple is blaming this on user activity.
  24. macrumors 68030


    Oct 19, 2010
    Buffalo, NY
    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'.
  25. macrumors 603


    Nov 5, 2009
    I have the bug, but I manage to turn it off quite easily once I noticed the moon next to my signal bar. I did not know it was a bug, thought it was me that pressed the DND thanks to the party. I have not experience yet what you are referring about it adjusting time and turning on; it does make sense and is still the same bug. Last year there was another bug akin the first week of the year. Is not the end of the world so no need to change to android. It's not like android is the best os neither. I don't mind waiting until Monday, but they should have as cortesy send an email to all AppStore account emails.

Share This Page