Slashdot Mirror

← Back to Stories (view on slashdot.org)

iPhone Alarms Hit By New Year's Bug

Posted by Soulskill on from the wake-up-and-smell-t dept.

An anonymous reader writes "Non-recurring iPhone alarms stopped working on January 1 for devices running iOS 4.02, 4.1, and 4.2.1. Apparently, it will fix itself by January 3, and the current workaround is to set the alarm to repeat. My girlfriend wasn't impressed, sleeping in, and I wasn't either, having to race her to work!"

2 of 405 comments (clear)

  1. No alarm? Thank god! by PolygamousRanchKid+ · · Score: 2, Interesting

    I bought my girlfriend an iPhone, and the damn thing seems to set off the alarm at random times.

    However, when I look at that thing, my Nokia N95 looks like crap in comparison. I'm no Apple fanboy, but I am really impressed with that thing.

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  2. Re:unreliable by scdeimos · · Score: 3, Interesting

    I am sure you can give us an example where the iOS time routines don't work as advertised.

    Here's a well-travelled and documented bug, which still hasn't been fixed: try editing a Contact entry to add a birth date for someone 77 years (I think) or older - good luck finding it in the calendar!

    The three outcomes I've seen for this include:

    1. Contact appears in the birthday calendar, but with the wrong birth date.
    2. The correct birth date appears in the birthday calendar, but with some other contact's name against it (wtf?).
    3. Neither the contact nor their birth date appear in the birthday calendar at all.

    Apple's date and time code needs review and TFA just demonstrates another example.