or Connect
AppleInsider › Forums › Mobile › iPhone › Apple admits New Year's alarm bug
New Posts  All Forums:Forum Nav:

Apple admits New Year's alarm bug - Page 3

post #81 of 135
Yeah this happened to me - I almost missed my flight from Tampa to NYC and my wife was late for work.

These little alarm bugs are starting to get annoying (same thing happened when the clocks adjusted for daylight saving), and frankly it's sloppy from Apple.

Do not overrate what you have received, nor envy others.
15" Matte MacBook Pro: 2.66Ghz i7, 8GB RAM, GT330m 512MB, 512GB SSD

iPhone 5 Black 32GB

iPad 3rd Generation, 32GB

Mac Mini Core2Duo 2.26ghz,...

Reply

Do not overrate what you have received, nor envy others.
15" Matte MacBook Pro: 2.66Ghz i7, 8GB RAM, GT330m 512MB, 512GB SSD

iPhone 5 Black 32GB

iPad 3rd Generation, 32GB

Mac Mini Core2Duo 2.26ghz,...

Reply
post #82 of 135
This isn't a new bug - remember the problem with the change from Summer Time to Winter Time bug? That was also in the clock app. So this thing isn't new as some people claim, it's just that it only affected non-Americans before now.

Still, it is only affecting iOS 4 - and because of various problems with this iOS I have not upgraded yet. I do think Apple is a little stretched at the moment.

As for those people claiming it isn't important, or isn't real, if Apple's internal staff acts like them then Apple really does have a problem. If nobody points out deficiencies, you'll keep on making them, and your reputation will be damaged.

Until Apple sorts out these silly little problems, I'm not replacing my iPhone 3G, nor am I going to upgrade to iOS 4, nor will I upgrade my iPad's software either (I want to keep my orientation lock).
post #83 of 135
Three pages of people complaining, but on an Apple forum, nobody remembers that this is a fairly complicated problem?

I've personally written event management software, and let me tell you - time zone management and recurring events are nontrivial things to figure out. That's why there are many libraries out there that try to do that for you, but sometimes even those don't work (although traditionally that's in esoteric situations, most places don't mess with their timezones).

This is a tough problem, that can be ridiculously hard to track down. Of course, I demand perfection from apple as much as any bloke, but this truly is a difficult problem, and as it turns out, their solution breaks. Strangely, it doesn't seem to use core libraries already built into the system (for iCal) to handle this. I can't imagine why not, that seems to work fairly smoothly.
post #84 of 135
Quote:
Originally Posted by SwissMac2 View Post

To make a mistake once, well, that happens to everyone; but to make the same mistake twice, well that's just careless. Apple have $50 billion in cash, are the world's biggest Technology company, and can't fix a simple bug like this?

Are Apple engineers incompetent, or has the boss just taken his eye off the ball? Bring back Woz! He'd have never let this happen.

The trouble with daylight savings time was the alarm not adjusting as a result of the time change - or perhaps changing when it should not have. I set an alarm for 2 pm on the day after the time change - and when the time change occurs either my alarm gets moved an hour as well to 1 pm instead of remaining at 2 pm or it stays at 2 pm as if the time of day did not change. (or something like that). This was a case of the alarms ringing at the wrong time.

Whereas the alarms not ringing at all would seem to indicate a different problem. and with all the lines of code that must go into such a system it is amazing that there are so few problems.
post #85 of 135
Quote:
Originally Posted by nvidia2008 View Post

WARNING: SETTING ALARM TO "REPEAT" DOES NOT SOLVE SOME PROBLEMS. MY ALARM FAILED TODAY AGAIN DESPITE BEING REPEATING ALARM.

DO NOT DEPEND ON IPHONE ALARM AT THIS STAGE FOR ANY CRITICAL APPOINTMENTS UNTIL THIS IS SORTED OUT.

Something else is the issue. The Apple spokesperson seems to be repeating (pun unintended) what blogs are reporting about it working fine if you set to repeating alarm, and about it working after Jan 3rd. This may not be the issue, it needs further investigation once the iOS engineers are back from holiday.

By setting it to a repeating alarm it seems to solve the issue when you test alarms during the same day. But somehow my alarm didn't go off this morning (Jan 2 2011) despite being a repeating alarm.

The indicated advice does NOT say that alarms will work on Jan 1 and Jan 2 when using a recurring option - it says that a recurring alarm with function properly starting on Jan 3. In other words saying that the problem only affects alarms - both singular and repeating - but only for instances which fall on the 1st or the 2nd.
post #86 of 135
Just curious but off any users that did experience this bug, do you have your date/time setting manually set or is it set to automatic? May have no impact, but i didn't write the code so I cannot guess The significance this might have. All I note is that some are affected and others are not. Btw, does anybody know what timeservers are used when date/time is set to automatic? I notice I can manually set my timezone to houston where I live but if i let the "autopilot" set it, it is set to Chicago. A difference for sure but both are in the same time zone. I just see it as interesting that it can be set to different things that are same. Just interesting that a gps equipped device sets it that way. Whatever... The only point being that I can only guess at what the programmers thatbuilt this stuff are thinking.

Hope it gets fixed before the next time change in a few months happens. Would presume a new ios will come out when iPad2 is released. Hope it is properly sorted for this bug and that it runs on all iOS devices
post #87 of 135
Quote:
Originally Posted by lilgto64 View Post

The indicated advice does NOT say that alarms will work on Jan 1 and Jan 2 when using a recurring option - it says that a recurring alarm with function properly starting on Jan 3. In other words saying that the problem only affects alarms - both singular and repeating - but only for instances which fall on the 1st or the 2nd.

"We're aware of an issue related to non repeating alarms set for January 1 or 2," Harrison said. "Customers can set recurring alarms for those dates and all alarms will work properly beginning January 3."

The advice clearly indicates, and personal testing by many people and blogs, show that on Jan 1 and 2 when using the recurring alarm, alarms work. However from January 3 alarms work regardless of whether they are set to recurring or not.

I have found the above to be true when I test out an alarm set to go off say, five minutes from now.

But it does not work for me overnight, the recurring alarm did not work on 11AM on Sunday Jan 2 and the normal alarm did not work on 11AM Monday Jan 3. Something is very screwy and I strongly suggest not to rely on the alarm for anything critical at this stage.

I wonder if "set time automatically" is affecting things because that comes from the carrier signal(?)

FWIW, my NightstandHD alarm went off normally this morning Jan 3rd. Will be using that now. The cool thing about the app is that you don't even have to have the app in the background for the alarm to go off.
post #88 of 135
Quote:
Originally Posted by sportytoes View Post

Just curious but off any users that did experience this bug, do you have your date/time setting manually set or is it set to automatic? May have no impact, but i didn't write the code so I cannot guess The significance this might have. All I note is that some are affected and others are not. Btw, does anybody know what timeservers are used when date/time is set to automatic? I notice I can manually set my timezone to houston where I live but if i let the "autopilot" set it, it is set to Chicago. A difference for sure but both are in the same time zone. I just see it as interesting that it can be set to different things that are same. Just interesting that a gps equipped device sets it that way. Whatever... The only point being that I can only guess at what the programmers thatbuilt this stuff are thinking.

Hope it gets fixed before the next time change in a few months happens. Would presume a new ios will come out when iPad2 is released. Hope it is properly sorted for this bug and that it runs on all iOS devices

It's a possibility. I've seen several iPhone4s have the date and time set to a weird "2000 BE" or something like that when set to automatic, and it kinda gets stuck on that. I didn't have the time to rectify it for those people, not sure what the solution was.
post #89 of 135
Quote:
Originally Posted by Dave Marsh View Post

Not everyone is experiencing this one-off alarm bug. I've tried this multiple times today on both my iPhone and iPad, and my one-off alarms have worked perfectly. So, there's something a bit more complicated occurring here that will take a bit more testing to narrow down and fix.

Would like to enquire, how did you test it on the iPad? Are you referring to iCal alarms? Did you test the Clock app on iPhone?

Quote:
Originally Posted by hill60 View Post

test alarm went off in Australia, 03/01/2011 (01/03/2011)

May I enquire, did you test it by leaving it overnight, or just test it by setting it a few minutes from now?

Quote:
Originally Posted by Eriamjh View Post

Apple isn't fixing it because everyone is on holiday. By Jan. 3, it won't be needed. Wait 'till next Jan 1.
I use a standard alarm clock. Only thing that kills it is a power failure.

It does seem like this whole thing is a little bit more complex. My Jan 3rd alarm didn't work *overnight*. Although test alarms today, Jan 3rd, go off if I set it within a few minutes of now.

There is definitely something else going on. The promise of it working on Jan 3 and everything being perfect, will bite Apple because some users will still be affected.
post #90 of 135
I have to agree that it is only common sense to not trust one alarm for important events (no matter what device or platform you are using), but it is disgustingly pathetic that it goes way beyond that to the level of paranoia when using my iPhone.

I have a simple solution that I have used for a while. It not only provides safely from mechanical unreliability, it also provides safety from human errors (which are actually far more common than these alarm clock bugs to be honest). I set both an alarm AND a timer on my iPhone to wake me up for work (one slightly offset from the other). If the alarm would fail for some reason, the timer is much less likely to suffer from the kind of glitches that might affect an alarm.
post #91 of 135
Quote:
Originally Posted by tigerpro View Post

I have to agree that it is only common sense to not trust one alarm for important events (no matter what device or platform you are using), but it is disgustingly pathetic that it goes way beyond that to the level of paranoia when using my iPhone.

I have a simple solution that I have used for a while. It not only provides safely from mechanical unreliability, it also provides safety from human errors (which are actually far more common than these alarm clock bugs to be honest). I set both an alarm AND a timer on my iPhone to wake me up for work (one slightly offset from the other). If the alarm would fail for some reason, the timer is much less likely to suffer from the kind of glitches that might affect an alarm.

Interesting solution. However, perhaps that still is depending on only one particular device for an alarm. iPhone has been the best iPod, PDA and phone I have ever used in my life. But it is not perfect.

For anything critical may I suggest that a clock radio, other alarm device or even old mobile phone (assuming the battery isn't dead) should be used as a backup.
post #92 of 135
The Dev Team Blog seems to be down at the moment, particularly the comments. Coincidence? Or people rushing to see how to fix this issues, maybe people worried that jailbreaking killed the alarm app.
post #93 of 135
Quote:
Originally Posted by elliots11 View Post

I do the same thing. Learned the hard way. This is still BS though because you can't always do dual alarm, like when traveling, nor should you be expected to do so at all. I hope they fix it properly, seems like such a basic app.
\

My thoughts exactly and what about the clock!!!! The time is right!!!! BUT the alarms fails to ring on the time set???? How cant the alarmclock not meet this small expectation . Seems to me that some one has made the alarmclock way to complicated.

And why make alterations to something that has successfully worked for YEARS without as much as a glitch!!!! YES MY ALARMCLOCK HAS WORKED FOR SEVERAL YEARS WITHOUT THIS STUPIDITY!!!
post #94 of 135
Quote:
Originally Posted by nvidia2008 View Post

Gaming on Windows presents several challenges.

Thanks for taking the time to write this. The last PC game I played was F1 Racing Championship in 2000 (!!!) so this is all quite interesting.
post #95 of 135
Today is the 3rd and my iPhone alarm didn't worked at all.

I have an iPhone 4 with 4.1 iOS and I set the alarm for today morning. Guess what? It didn't worked at all.

What's the deal with this? Is it so complicated to do a reliable alarm clock software or is someone at Apple trying to do a practical joke???
post #96 of 135
If you set the timer before 3 of January wont it go off on the 3 of January.

However, if you set the timer after midnight in 3 of January will it work. Go figure!
post #97 of 135
Quote:
Originally Posted by Rank Xerox View Post

If you set the timer before 3 of January wont it go off on the 3 of January.

However, if you set the timer after midnight in 3 of January will it work. Go figure!

Thanks for the tip. Will try this tonight.
post #98 of 135
Quote:
Originally Posted by c0h1b4 View Post

Today is the 3rd and my iPhone alarm didn't worked at all.

I have an iPhone 4 with 4.1 iOS and I set the alarm for today morning. Guess what? It didn't worked at all.

What's the deal with this? Is it so complicated to do a reliable alarm clock software or is someone at Apple trying to do a practical joke???

What time zone are you in? Did you set your date and time to "automatically set"? Curious.

Yes, it's kind of embarrassing for Apple, unfortunately.
post #99 of 135
i guess my wife, mother in law and i are some of the lucky ones. All of our alarms worked the whole weekend.
iPhone 4 32gb full updates on ours. moms is 3gs on most recent ios
post #100 of 135
Well, it's 1/3 and my wife's alarms didn't go off this morning (iPhone 3GS). She has alarms set for 6:00, 6:05, and 6:10 (she's pretty anal). The only reason she woke up is because she has her backup standard alarm clock on the nightstand.

WTF Apple?
post #101 of 135
Quote:
Originally Posted by Mazda 3s View Post

Well, it's 1/3 and my wife's alarms didn't go off this morning (iPhone 3GS). She has alarms set for 6:00, 6:05, and 6:10 (she's pretty anal). The only reason she woke up is because she has her backup standard alarm clock on the nightstand.

WTF Apple?

As I posted above:

Quote:
If you set the timer before 3 of January wont it go off on the 3 of January.

However, if you set the timer after midnight in 3 of January will it work. Go figure!
post #102 of 135
Quote:
Originally Posted by Onhka View Post

Perhaps you should abide by the old English idiom, "People in glass houses should not throw stones."
By the way, is it true that your mum still has to remind you every week to take the refuse out?

Perhaps you should get over it mate.

Thank you for your remarkably adult response

Could you please explain how you made the connection between our programme scheduling software for the World Service and the BBC's payroll software? Thanks.

No, I've been holding down a job, bought my own home, driving cars & motorcycles and taking out the rubbish and the recycling for a long, long, time - probably longer than you've been walking this earth I shouldn't wonder.
post #103 of 135
Quote:
Originally Posted by solipsism View Post

Another downside is the number of people who disparage you simply because you are successful.

Well which is is??? disparaging the successful or what you said earlier?
Quote:
"This is pretty shameful as it’s a dumb bug to repeatedly have crop up now. It’s not like they are a startup.

What does this really take from Apple to detect ahead of time? One iOS developer spending an hour setting the clock ahead to these milestone dates to see if the alarms go off as they should?" End quote
You seem to say two different things......
If this were an Android issue you all would be Blasting Google and talking about fragmentation...but the Android alarms worked......

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply
post #104 of 135
Quote:
Originally Posted by jkmassel View Post

Three pages of people complaining, but on an Apple forum, nobody remembers that this is a fairly complicated problem?

I've personally written event management software, and let me tell you - time zone management and recurring events are nontrivial things to figure out. That's why there are many libraries out there that try to do that for you, but sometimes even those don't work (although traditionally that's in esoteric situations, most places don't mess with their timezones).

This is a tough problem, that can be ridiculously hard to track down. Of course, I demand perfection from apple as much as any bloke, but this truly is a difficult problem, and as it turns out, their solution breaks. Strangely, it doesn't seem to use core libraries already built into the system (for iCal) to handle this. I can't imagine why not, that seems to work fairly smoothly.

Programming IS certainly complicated and for as long as software is written it will contain bugs whether written by Apple, Microsoft, IBM or anyone. Some bugs, like "If I draw a new object, move it 20 pixels, then shade it green, switch the app to inactive, the click back in the document, give the object a drop shadow and then duplicate it, then sometimes the app crashes may be impossible to replicate! The causes of some bugs are easy to understand (divide by 0 for example) and some can be very, very difficult to fix. The thing about this bug though is that:

*) The number of days in any year is known precisely as are the days in a month.
*) All leap years and their effects are known in advance
*) Times for the beginning and ending of Daylight Savings Times are published for all countries well in advance (or there would be no chance at all of getting this right at all!)
*) The choices in the Alarm Clock app are decided by Apple, namely: you can set a one off alarm or a repeating pattern with a finite number of options.

Therefore given a single TZ, only certain things need testing and they are all knowable in advance. Considering the complexity of software that Apple has written (Core Animation, Spotlight, Core Video, Aperture, Final Cut, etc. etc. etc.) this should be trivial and saying that it is "a truly difficult problem" is failing to address what's going on. As I said in a previous post, our software for the BBC had to handle all this kind of thing, including stopping people setting a program to broadcast at, say 1:30am in a country where the DST came into force and meant that 1:30am "happened twice" after the clocks went back. It also had to handle the same situation where 1:30am would not exist when the clocks change the other way and the clocks jumps from 1am to 2am. Again, all this is known and mathematically predictable years in advance and can and should be tested for.

If you read Apple's Framework documentation for NSDate, NSTimeZone and NSCalendar you will see the depth of thinking about dates that has gone into it by Apple and others so it's not as though they are not aware of the complexity in coding for date calculations which makes something as simple as "When I cross into a new year, this bug happens" such a surprising error.

As for "get over it" or not, well, how important this bug is to each of us depends on how we use Apple's mobile devices. If you never use the Alarm Clock app it will be irrelevant, if you rely on it for critical events then it will be significant and just calling people "stupid" for relying on Apple's software is hardly the point.

I don't expect perfection from any software company, just the very best they can do, but falling over on something of this nature is rather elementary for a company employing some of the finest software engineers on the Planet.
post #105 of 135
Quote:
Originally Posted by geekdad View Post

If this were an Android issue you all would be Blasting Google and talking about fragmentation...but the Android alarms worked......

Yes, the Android alarm will wake you in the morning right on time. But Android will still be Android.
post #106 of 135
Quote:
Originally Posted by Quadra 610 View Post

Yes, the Android alarm will wake you in the morning right on time. But Android will still be Android.

Didn't you hear? On January 4 2011 all Android phones will become iOS phones.
It's a feature, not a bug!

But seriously though Apple dropped the ball on this one, particularly so in saying everything
would work fine on Jan 3rd, which is not the case... :-|
post #107 of 135
Quote:
Apple admits New Year's alarm bug

This one is kind of strange. Any programmer worth his salt will set up unit tests around time code that would easily pick this kind of problem up. Maybe this is something to do with the way the software interprets the time result from the hardware clock.
post #108 of 135
Quote:
Originally Posted by dlcmh View Post

Thanks for taking the time to write this. The last PC game I played was F1 Racing Championship in 2000 (!!!) so this is all quite interesting.

This is what console gaming has done to the gaming industry:
http://www.youtube.com/watch?v=Pblj3JHF-Jo
post #109 of 135
Quote:
Originally Posted by TedK View Post

It's disappointing to read these posts from people like Onhka and Wonder when they're throwing around words like stupid and moron in this sort of open, opinion-based forum. People are entitled to express themselves without being jumped on. If a poster is upset by an Apple bug, esp. a very basic and annoying one, then so be it. There's no need for childish name calling...

Well spoken good sir.

Back to the original topic, I too experianced this issue both days. Using an iPhone 3GS 32GB, latest iOS version, and NO jailbreak.

Also, being New Years Eve weekend I had a date that stayed over a couple nights. She had noticed I use almost all Apple products at home (iMac, Mac mini, iPhone, iPad, Apple TV) and asked why. I mentioned it's mainly because they're so reliable. Due to sleeping in too late both mornings, because the alarm didn't go off, I have a hunch she's not taking that "reliable" point too seriously. Doubt she'll be a switcher anytime soon. Way to go Apple!

But at least Apple's alarm issues beats the Pocket PC/Windows Mobile alarm issues I had 2000-2007 on several models I owned. And I was not alone. It was the norm that various alarms wouldn't go off on many users devices from all device vendors, a few times a week at random in my case, and as far as I'm aware Microsoft never was able to figure the issue out. They even offered a reward at one point for anyone that could figure it out. Well, that's Microsoft for you!
IF Reading_Comprehension_Skills = "On" THEN Please_Respond ELSE Take_Nap
Reply
IF Reading_Comprehension_Skills = "On" THEN Please_Respond ELSE Take_Nap
Reply
post #110 of 135
Quote:
Originally Posted by nvidia2008 View Post

Didn't you hear? On January 4 2011 all Android phones will become iOS phones.
It's a feature, not a bug!

But seriously though Apple dropped the ball on this one, particularly so in saying everything
would work fine on Jan 3rd, which is not the case... :-|

Maybe the alarms didn't work because you were holding it wrong for them to work.........
My wife's alarm did not work on her iPhone and she was late for work....not a big deal all things considered. But I had to rub it in that my alarm on my EVO worked perfectly.
Apple does get a little smug sometimes in the response to consumer complaints....

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply
post #111 of 135
Quote:
Originally Posted by geekdad View Post

Well which is is??? disparaging the successful or what you said earlier?
Quote:
"This is pretty shameful as its a dumb bug to repeatedly have crop up now. Its not like they are a startup.

What does this really take from Apple to detect ahead of time? One iOS developer spending an hour setting the clock ahead to these milestone dates to see if the alarms go off as they should?" End quote
You seem to say two different things......
If this were an Android issue you all would be Blasting Google and talking about fragmentation...but the Android alarms worked......

Startup refers to a new company, not one that is a failure. In fact, all successful companies came from the successes of initial startups.

Ill use an example. A company has trouble securing more than 200k NAND modules for their product and ends up not selling as many as they could do to a lag in production due to this component issue. That is perfectly understandable for a company that is fairly new and limited in every way, but for Apple or HTC or Nokia not be able to secure more than 200k NAND units, well that would be shameful.
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
post #112 of 135
Quote:
Originally Posted by mimsyswallows View Post

Is this the third time, or am I mis-remembering? What is so hard about doing the alarm app right?

Yeah, have a feeling that if we see any more of these bugs pop up we may see a class action lawsuit!
post #113 of 135
Quote:
Originally Posted by solipsism View Post

Startup refers to a new company, not one that is a failure. In fact, all successful companies came from the successes of initial startups.

Ill use an example. A company has trouble securing more than 200k NAND modules for their product and ends up not selling as many as they could do to a lag in production due to this component issue. That is perfectly understandable for a company that is fairly new and limited in every way, but for Apple or HTC or Nokia not be able to secure more than 200k NAND units, well that would be shameful.

I think you missed my point...It was YOUR quote about the start up and it being shameful for Apple to not fix this bug TWICE...That was not my quote. In one post you said it was shameful for Apple to have not fixed this by now...then 2 posts down you insinutaed that people pick on Apple becuase they are successful.......you can't have it both ways...you said to different things in 2 diferent posts....that was my point but no worries......it is a great new year!

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply
post #114 of 135
Quote:
Originally Posted by geekdad View Post

I think you missed my point...It was YOUR quote about the start up and it being shameful for Apple to not fix this bug TWICE...That was not my quote. In one post you said it was shameful for Apple to have not fixed this by now...then 2 posts down you insinutaed that people pick on Apple becuase they are successful.......you can't have it both ways...you said to different things in 2 diferent posts....that was my point but no worries......it is a great new year!

As I pointed out and you just stated, [I] said [two] different things in 2 diferent posts. They are separate issues and therefore can both exist at the same time. Again, startup does not imply failure.
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
post #115 of 135
Quote:
Originally Posted by solipsism View Post

As I pointed out and you just stated, [I] said [two] different things in 2 diferent posts. They are separate issues and therefore can both exist at the same time. Again, startup does not imply failure.

Well just to keep things honest. I did not infer a "start up" implys failure. You did in post #5 and I quote you:

"This is pretty shameful as its a dumb bug to repeatedly have crop up now. Its not like they are a startup.What does this really take from Apple to detect ahead of time? One iOS developer spending an hour setting the clock ahead to these milestone dates to see if the alarms go off as they should?"

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply
post #116 of 135
Quote:
Originally Posted by geekdad View Post

Well just to keep things honest. I did not infer a "start up" implys failure. You did in post #5 and I quote you:

"This is pretty shameful as it’s a dumb bug to repeatedly have crop up now. It’s not like they are a startup.What does this really take from Apple to detect ahead of time? One iOS developer spending an hour setting the clock ahead to these milestone dates to see if the alarms go off as they should?"

What a weird world you live in. I implied nothing of the sort and you’ve somehow many two separete comments into some Voltron comment that doesn’t exist.

As noted with my previous example, a startup would have less resources at hand to deal with certain issues. You inferred “startup” means failure simply because they have less resources, when I implied the exact opposite, that Apple has failed on this issue by virtue of the fact they do have the resources that a “startup” does not.

PS: What was your new year’s resolution? To give Teckstud your account?
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
Dick Applebaum on whether the iPad is a personal computer: "BTW, I am posting this from my iPad pc while sitting on the throne... personal enough for you?"
Reply
post #117 of 135
Everyone in our house got spanked this morning. Wife late for work and I was late getting my daughter back to school. We new about the issue but also read that it was resolved after Jan. 2. Not the end of the world, but we all really depend on these things to work.
post #118 of 135
Quote:
Originally Posted by Firefly7475 View Post

This one is kind of strange. Any programmer worth his salt will set up unit tests around time code that would easily pick this kind of problem up. Maybe this is something to do with the way the software interprets the time result from the hardware clock.

Hard to say what caused it but I wouldn't be surprised if it was a bug introduced during some power management optimization. The Clock app must be running in the background all the time so they might have been doing some tricky suspending routine that came back to bite them.

Life is too short to drink bad coffee.

Reply

Life is too short to drink bad coffee.

Reply
post #119 of 135
Quote:
Originally Posted by solipsism View Post

What a weird world you live in. I implied nothing of the sort and youve somehow many two separete comments into some Voltron comment that doesnt exist.

As noted with my previous example, a startup would have less resources at hand to deal with certain issues. You inferred startup means failure simply because they have less resources, when I implied the exact opposite, that Apple has failed on this issue by virtue of the fact they do have the resources that a startup does not.

PS: What was your new years resolution? To give Teckstud your account?

LOL you inferred the startup and failure in your post not I...... you just don't like being called out for conflicting posts with conflicting statements. Not a problem...don't really care. Have a great new year! Why bring up Techstud? Do you miss him?

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply

Tallest Skil:


"Eventually Google will have their Afghanistan with Oracle and collapse"

"The future is Apple, Google, and a third company that hasn't yet been created."


 


 

Reply
post #120 of 135
Quote:
Originally Posted by radster360 View Post

I don't think it is just 1.1.11 or something special about 2011 issue. Looks like the bug might have to do with Jan. 1 and Jan. 2 of every year. Why else would they fix it, since the dates have already passed, if it was for an absolute year. I hope they test it out for every year.

It might even have to do with the fact that these days were on the weekend as opposed to weekdays, which follow different rules for recurring alarms. I wouldn't be surprised if there weren't some obscure bug in the "do alarm / don't alarm" logic involved with recurring/non-recurring, weekday/non-weekday, pathways which only gets tripped under very peculiar circumstances.

Some bugs, like Y2K, are not so much programming bugs as they are paradigm problems that result in fairly "sensible" bugs. By that, I mean you can make sense out of them by just observing the symptoms and understanding the principles involved. But some other bugs cannot be understood in this manner. Some bugs are just plain screw-ups by the programmer that result in strange manifestations. When you face one such bug, you can't just stand outside of the box and work your way to the explanation. You have to dive into the code. That may very well be the case here.

Thompson
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: iPhone
AppleInsider › Forums › Mobile › iPhone › Apple admits New Year's alarm bug