As long as we are giving credence to anecdotal evidence, my alarms went off as usual this morning. A little extra sleep would have been nice but no alarm problems here. 
Got a tip for us?
Let us know
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
- Thread starter MacRumors
- Start date
- Sort by reaction score
As long as we are giving credence to anecdotal evidence, my alarms went off as usual this morning. A little extra sleep would have been nice but no alarm problems here.
Are they set as recurring alarms?
I do NOT blame Apple for this. It is VERY hard to debug programs that are to sense future clock/calendar readings. The answer, and not just for this reason, is reform of our clock settings and calendar readings to permanent universal constants (easy to do technically, but not administratively). Here's the page:
http://henry.pha.jhu.edu/calendar.html
Although, since iOS is a derivative of Mac OS X and Darwin these issues should not be occurring.
Exactly what are the problems with iTunes (except from the fact that you can't switch between different iTunes libraries, e.g. lossy and Losless) without relaunching iTunes
I use itunes for my +50 GB music library, I often use it to convert and stream my music to my Denon receiver. So far I haven't encountered any bugs, perhaps some missing features, but nevertheless it's as far as I'm concerned great program with a nice interface and easily usable features
Well, I would blame Apple (or the developer, but then Apple paid him to do his job). No need to do any calendar reform for this. This looks like a straightforward application bug, most likely caused by the fact that 1st and 2nd of January 2011 are actually in the last week of 2010, and the first week of 2011 starts on the 3rd (that is the only explanation I can think of why the app would go wrong on Jan 1st and 2nd but fix itself on the 3rd).
Both MacOS X and iOS have functions to handle everything that is date and calendar related correctly; the problem is that the program developer has to use these functions correctly.
Exactly what are the problems with iTunes (except from the fact that you can't switch between different iTunes libraries, e.g. lossy and Losless) without relaunching iTunes
I use itunes for my +50 GB music library, I often use it to convert and stream my music to my Denon receiver. So far I haven't encountered any bugs, perhaps some missing features, but nevertheless it's as far as I'm concerned great program with a nice interface and easily usable features
I guess you ignore the constant freezes, bad UI, lags...
Don't blame Apple for problems debugging, blame them for writing the buggy code to start with.
A few bytes of prevention is worth gigabytes of cure.
Gotta love these made up stories. I'm willing to bet that more than 50% of the posts that said they were late for whatever reason due to this one bug are nothing but blatant lies just so they something to bitch about, even on the new year. If their time was so important to them they would have a backup plan and not rely on a portable device with limited battery life to keep them on track. I call it BS.
Gotta love these made up stories. I'm willing to bet that more than 50% of the posts that said they were late for whatever reason due to this one bug are nothing but blatant lies just so they something to bitch about, even on the new year. If their time was so important to them they would have a backup plan and not rely on a portable device with limited battery life to keep them on track. I call it BS.
Yes, always use two alarms but regardless, this is an issue that should not happen.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5)
Unit testing. There is no excuse.
henrystar said:
Unit testing. There is no excuse.
Dude, I can smell the kool-aid on your breath.
Hard or not, it still should have been verified. Its not like a 9.99 piece of tech, these phones cost hundreds of dollars, and therefore DEMAND the best coding and programming. If a Casio watch from 1985 can do it, then why not an iPhone that is multiple orders of magnitude more advanced? Sorry, the excuse you offer just does not wash.
The bug really is egregious and this is a very very poor oversight from Apple. However, software bugs happen all the time, and to anyone.
Hope the fix comes out soon.
Apple doesn't sell any phone for £699 stop buying black market...especially when you can get it cheaper.
It's called Apple Inc, why are you inventing a new name for them. They knew about the previous manifestation of the bug (and fixed that) not this one. If you're gonna cite something read it first. There is lot of work involved in transitioning a beast like Final Cut Studio to cocoa which takes time (2-3yrs or more) and they've been/are still working hard on it...it's not like they are just sitting around playing paper toss.
You just have to be joking
Hope the fix comes out soon.
Apple doesn't sell any phone for £699 stop buying black market...especially when you can get it cheaper.
Or Final Cut Pro, both of which are STILL in 2011 CARBON based 32 bit applications. While 64 bit may not be needed for iTunes, the fact that they are selling pro apps apps such as Final Cut Pro made with Carbon is an utter disgrace.
Hell, even Adobe moved to Cocoa already. If Adobe can do it, why can't Apple Consumer Electronics? Oh yeah, because they don't care about anything other then iOS, and even then I don't think they care much about the details like a correctly functioning clock.app
The last time there was a bug with clock.app a few months ago, Apple Consumer Electronics was warned MONTHS before about it. Yes MONTHS, and they still did nothing.
Oh, and Fortune / CNN is reporting that Apple Consumer Electronics did know about this bug as well.
Link
It's called Apple Inc, why are you inventing a new name for them. They knew about the previous manifestation of the bug (and fixed that) not this one. If you're gonna cite something read it first. There is lot of work involved in transitioning a beast like Final Cut Studio to cocoa which takes time (2-3yrs or more) and they've been/are still working hard on it...it's not like they are just sitting around playing paper toss.
You just have to be joking
Because they scrambled to fix the DST bug. They waited until it hit the US while the rest of the world that uses DST waited.
He likely bought it out-of-contract or unlocked. That's not black market. Learn how the iPhone is sold in other countries.
Yes, I agree, it's an issue that "shouldn't" happen, but since we're dealing with computer generated products, crap can happen, simple as that. Every single person on this forum has had an issue one time or another with their Mac or the Windows machine, what do they do about it? Kill Steve Jobs or Steve Emballmer? No, they just deal with it and move on. It's silly for this forum to go into labor over this. That's why I know most people here are lying about these late stories. It's not serious enough to cause such a ruckus.
It looks like the fix is coming on 3 January.
Hmmm. There were lots of posts around here calling Adobe "lazy" (or worse) for Adobe's Cocoa porting schedule. It looks like Apple is held to a lower standard.
It's a time-based issue that shouldn't happen because of what iOS is derived from. That's the issue.
Last edited by a moderator:
It looks like the fix is coming on 3 January.
Hmmm. There were lots of posts around here calling Adobe "lazy" (or worse) for Adobe's Cocoa porting schedule. It looks like Apple is held to a lower standard.
I know about the Jan 3 fix, i'm hoping for a more permanent fix as opposed to a circumstantial.
As for the programming, a lot of non-programmers like to talk like programmers in general so i'm not surprised.
Well, it'd be nice if it stated that in your profile to the left of the post, wouldn't it?
...just as it would be nice if you didn't assume i didn't know what i was talking about.
Last edited by a moderator:
i still don't understand how something like this happens. i use my iPhone to wake me up everyday. apple needs to fix this today!
I'm confused by this claim. I went to bed last night at 10:50. Set an alarm for 7:40 this am and it went off without a hitch?
What am I missing?
What am I missing?
Are you surprised? Apple are masters of eye candy but basic functionality just isn't their thing
Ha ha ha!