I for one am amazed that they managed to screw up so many things on an alarm clock app.
There can't be that much ****ing code behind it, seriously.
There can't be that much ****ing code behind it, seriously.
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
Yes, because Apple can only focus on one thing at a time. So the people who approve apps for the app store should do what, fix bugs in the iOS codebase instead? Do you understand that a multi-national, multi-billion dollar company that is the 2nd largest corporation in the United States, 2nd only to Exxon-Mobile, has many departments, groups, and business units? Each one handles something else, so you can't just say "focus less on apps and more on fixing bugs" because they are two completely different groups/departments.
Apple is sitting on $52 billion in cash, so it's not like they can't go out and hire more programmers. And Apple has not "lost the mobile space to android". Where do you get this crap? Android's growth has come exclusively at the expense of RIM, Palm, and Windows Mobile. What has hurt Apple from selling more iPhones is the exclusivity with AT&T. It has nothing to do with internal company resources.
Please get an education.
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)
Good going Apple... I was 1 hour late to work today.
Good going Apple... I was 1 hour late to work today.
You people waited two years for the iPhone to get the most basic function - cut and paste. I think you'll get through this. You may need some therapy, but you'll certainly get through this...
Please get an eduction? You do understand the difference between market cap and company size? Don't you? Its a simple concept that you seem to have no conception of. Just because a company has a large market cap, does not make it the "second largest" in the United States. All this means is that the sum total of its shares, if taken at current market value, will equate into X amount of dollars.
Again, this has nothing to do with making Apple "2nd largest corporation in the United States", as valuation does not correlate into corporation size. They are two different concepts.
I hope I was able to provide you with some education this morning.
Also, I do understand. I think that Apple has lost focus, and this permeates the entire ecosystem. Its my belief that the focus is no longer of making great software and proving for a thriving ecosystem; rather I think it more about control and seeing how shiny they can polish the chrome bits while neglecting (or barley tending to) the hardware/code base underneath.
re: the apple response posted in the update: another classic. they don't even bother to say if they'd even try and fix it. just "oh, customer, just ignore it and pretend like it doesn't exist" just like the antenna. if they had any kind of accountability to a business environment they'd be screwed. it makes me laugh
Maybe you weren't referencing me directly, but I'm pretty tired of being called a liar. Obviously my situation was not as important or critical and being late wouldn't have meant being fired or missing a plane and purchasing another ticket, it would have meant time lost with family members that I have not seen in 2 years at a critical time where I'm about to deploy to Afghanistan. Family time is very important to me right now.
How dare you call us liars. This is one night where the vast majority of the population (at least in America) have had some form of alcohol in celebration. And because of this we get labeled as drunks. Like I said, I was out with friends from my unit who I've already spent 1 year in Iraq with and am about to spend another year in Afghanistan with. Yeah, we drank a little more than normal. So what. And again, I was not at my own house and none of them had to be awake in the morning so I knew I couldn't rely on anyone else to wake me up. My iPhone was my only option.
Am I upset about? A little. It wasn't a life altering deal for me. Am I going to switch to another phone because of this. No. I love the Mac ecosystem and OS too much to switch over a bug like this. I understand bugs happen. Am I making this up just to bitch at Apple? No. I don't bitch, I grumble under my breath and then do what my NCO ordered me to.
How dare you call us liars. This is one night where the vast majority of the population (at least in America) have had some form of alcohol in celebration. And because of this we get labeled as drunks. Like I said, I was out with friends from my unit who I've already spent 1 year in Iraq with and am about to spend another year in Afghanistan with. Yeah, we drank a little more than normal. So what. And again, I was not at my own house and none of them had to be awake in the morning so I knew I couldn't rely on anyone else to wake me up. My iPhone was my only option.
Am I upset about? A little. It wasn't a life altering deal for me. Am I going to switch to another phone because of this. No. I love the Mac ecosystem and OS too much to switch over a bug like this. I understand bugs happen. Am I making this up just to bitch at Apple? No. I don't bitch, I grumble under my breath and then do what my NCO ordered me to.
Last edited:
More Complicated Than You Think
I wish the Apple Software Engineers could release the application code required for the Alarm Clock. I'm sure that those that think this is such an easy thing would be surprised at the complexity of the code. Could this have been caught during a code review? Perhaps - but some human being was not able to think of every condition possible. Move on with your gripes.
Signed - An Ex-Software Engineer.
I wish the Apple Software Engineers could release the application code required for the Alarm Clock. I'm sure that those that think this is such an easy thing would be surprised at the complexity of the code. Could this have been caught during a code review? Perhaps - but some human being was not able to think of every condition possible. Move on with your gripes.
Signed - An Ex-Software Engineer.
A 15$ Casio Watch seems to handle the complexity of an Alarm clock function with blistering efficiency - or any Nokia phone for the last 10 years for that matter
I like Apple - but this is an embarrassing bug - especially because it is not the first one. Makes me wonder, if they are any more hidden treasures in the deep jungle of the Alarm code spaghetti
1. Why did my first watch, a 1985 Casio never miss an alarm. If 1985 code worked flawlessly, then why can't 2010 code?
2. Why not push an update? CNN is reporting that Apple knew of this issue BEFORE it happened. Can't code be fixed and updates sent out before a flaw affects users?
Surely, if said human being had any common sense he / she would have a list of significant 'events' to look out for in the code. Such as- when the year changes from x to x+1 and when clocks around the world change due to DST etc. These aren't new phenomena and are pretty fundamental to the way an electronic alarm needs to keep track of time. You don't need to be a software engineer or be able 'to think of every condition possible' to have a little common sense or foresight!
I'm not whining about it, just making what I think is a fairly obvious point.
Last edited:
This has just hit the BBC main news at 5:40pm! Sign of the times I guess, but I would be very surprised if we didn't get an update by tomorrow morning.
Umm all the other phone out there work just fine. This just means you can not use the iPhone for mission critical stuff. It is the only phone that has repeated failed in that department. None of the other phones do....
You care to answer why across 4 cell phone, and 2 computers none of them ever missed an alarm proving they were turned on. This included reoccurring alarms.
Screwing up an alarm clock is pretty unacceptable. The code for that has been around for so long that they should already of had it to be able to us. It is not like it changes that much.
If time matches alarm time
If Day matchs alarm day (weekday, weekend ect)
Alarm go off.
Really it is that simple. It is not exactly rocket science coding. Fairly simple coding for the alarm function. All the more advance stuff is pulling the time, day, and running the alarm but those should be single function calls. Code for the alarm should be less than 50 lines of code (50 is being be REALLY NICE)
See that tells me yet again why Apple should not be trusted for anything mission critical. They make no effort to fix those bugs when they find out about them or they just let them go out.
So if Apple is screwing up something this simple on an iPhone why the hell would I want them running my servers or using them as my computer. Those are more mission critical to me than lets say an alarm function but goes along the same principle.
IT departments can and will sight this as yet another example of why they will not use or trust Apple products.
This bug caused me to miss my flight home. Rebooking has cost me 500 euros!
Does anyone know an email i can complain to, their website is spectacularly unhelpful... I have a dutch iphone 3gs.
What do you recon the chances of any compensation are.
Why on earth would apple be responsible for your own failure to have an alternate backup. Can you sue your car manufacturer if the car fails to start one morning?
Of course, you assume the bug is in the alarm clock code. Since there is complex interaction going on in an OS that has many processes 'always on' (phone, message, mail, push etc - yeah not a BIG deal, but you get the idea),
its not hard to imagine that it could be a bug in some other process that INTERFERES with the alarm process.
Not saying it is, but just pointing out that the reason may not be what you think.
And I understand that it could be a simple mistake, but I don't see why that necessarily means something catastrophic. On that basis, humans should never do anything important or significant. Chronic simple mistakes, maybe.
Can you sue if the airbag does not deploy? While hardware failures are expected, are software bugs that Apple knew about before they were an issue likewise expected? To me the point here is the inaction of Apple to a known issue, as per CNN's reporting. Apple knew of the issue, Apple had the ability to fix the issue and Apple had the ability to push out a fix via iTunes. However - APPLE DID NOTHING.
Um....why did you quote me? What the hell does your response to my post have to do with the alarm clock fluffing up?