Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iPhone Clock Bug Prevents Alarm Triggers after New Year's

farleysmaster said:
I'm slightly concerned about someone trusting the life of their child to a single piece of consumer electronics.

I also can't help think that everyone who's commented on this story with either point of view is a little weird.

It's right to expect an alarm clock to work, and it's also right to allow A LOT of time for catching flights.
Click to expand...

Do you expect someone to wait at the airport for 4 hours for a routine flight just because Apple can't program right?
 
hmmm, still didn't work here. ignored the alarm completely when rolling through midnight. worked when i set the alarm for the same day though (i.e. after midnight for 00:05).
 
eaf7s said:
I found this hilarious. My boyfriend works at an Apple store and had to be there at 9am New Year's Day, and said that literally half the staff were way late and they just started calling them in advance of their shifts, since so many of them used their phones as their alarms.
Click to expand...

Beautiful. Must.. release.. iBreathe to remind iPhone users when to breathe. Timebombed to stop working 24 Jan 2014 (shhh don't let the Apple code auditors hear that, I'm sure as long as I don't repurpose the volume control it'll get through).
 
If you work for Apple's Clock department...

If you work for Apple in the Clock department, do you get docked for being late to work today?
 
Just as a pleasant note, I've just tested the alarm set without a repeat and it works fine. Seems it does fix itself. Freaking weird though.
 
40yo wind-up mechanical alarm clock here, just tested and alarms work fine. Although I can't put my finger between the bells and the dinger otherwise the signal is muffled but apparently this is by design.
 
brop52 said:
Just tested it two minutes ago. Didn't work. Still only works as a recurring alarm.
Click to expand...

Interesting. Doesn't bode well for the "fixed on the third" theory.

We've confirmed the recurring fix here, but will have to wait a few hours until the third to test the "week number" theory here.
 
JoeG4 said:
If they knew about this ahead of time, I wonder why they didn't do some kind of emergency last minute patch to save their asses.

Ahh yes. Good ole' Apple.
Click to expand...

Because they were too busy ridding the app store of the scourge of apps that allow the use of volume buttons as a camera shutter. This was waaaayyy more important to Apple Consumer Electronics. Apple is all about flexing its power, be its strong-arming app Dev's or using their friends to do armed raids by knocking in the doors in of tech bloggers.

Things like reliable software or fixes for KNOWN issues have to wait until Apple is done with their collective power trip.
 
It would really suck to have been affected by this, however it's always good to have a back up alarm. I usually have my iPhone and BlackBerry (work) set to go off around the same time. Occasionally I'll set my alarm clock as well. I've had each fail on separate occasions but never all at once. *knock on wood*
 
I have little to no knowledge of programming, so I have no clue why this would actually happen. Obviously it's a programming error of some sort. But am I the only one that doesn't see why Apple, or anyone for that matter, would test to see if the changing of the year would effect the alarm triggering? Do people honestly expect Apple to make the device think it's a different year and then see if it still works? Seems like if the clock was developed properly then that wouldn't matter. And I think it's safe to say that the developer thought he/she did develop it properly.

Programming error yes. But testing error? Give me a break. And for the record, I woke up an hour late today as well.

One last thing... Clock joke.
 
proves that iphone users are idiots

haven't any of you realized that the little $5 alarm clocks from wal mart are more reliable than your iPhone alarms? COME ON!!

And ever since SNOW leopard, apple has not had solidly made software. They are starting to go down as a corporation. Someone earlier stated that apple is losing focus. Instead of focusing on solid software, they are now focusing on control.

I used snow leopard for a couple months, then I had to downgrade to regular leopard because the bugs were overpowering the little changes in the gui.

Apple will be lucky if they get anymore money from me.
 
Last edited:
Just tested 2 alarms, 12:05 & 12:10, and both worked fine... I have one more set for 12:18 just to triple check, but as Apple said, everything seems to be back to normal on the 3rd! Thank God I had nothing to wake up for the last two mornings. Gotta love vacations!

I am kind of hoping my alarm doesn't go off in the morning so I have an excuse to be late... If my boss asks, I will just say "Didn't you see all of the negative press about the iPhone alarm? It's not my fault!" haha jkjk
 
Hmm, I set a NEW alarm for 7 AM this morning (Jan 3) and it doesn't work. I am wondering how many minutes were spent on coding this clock.
 
January 3rd in the UK and the alarm didn't go off for the third consecutive day.
 
I was able to get both repeating and regular alarms to go off. Anyone who is still having trouble, try deleting the alarm and making a new one.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back