Date Bug in iOS 11.1.2 Causing Crash Loop on iPhones as December 2 Hits [Updated]

[NaOH]

Yes, but it was actually Beta 6:

https://twitter.com/niw/status/936889903752790018

Apple essentially made it official on an emergency overnight basis as opposed to having it released at the regular time with the other updates.

Ah gotcha.

Guess it’s not fully baked, then.

 

[Bryan Bowler]

What haopened to “it just works”?

 

[szw-mapple fan]

Absolutely unbelievable. Apple used to be untouchable. Is Android better now? This is sad.

Come on. Used to be untouchable? Date bugs has been in iOS for god knows how long, always showing up here and there over the years.

 

[Kid Red]

Jeesh, does Apple even QA anymore?

 

[BWhaler]

...and the hits keep coming with Apple”s shoddy software.

And to think, before the 2017 releases, all we had to worry about was the lack of innovation. Oy.

 

[gnasher729]

this is sad... i swear quality control is going down the drain, and its not just apple. not even within technology companies. this seems to be a trend for any corporation

This is not a question of quality control, it is a question of quality. I really cannot figure any way to have a bug that crashes at this time without doing it intentionally.

 

[Abazigal]

Fact is Apple in 2017 has fundamental problems in the way it makes system software. The finesse and efficiency is not there anymore. MacOS is unrefined and buggy and slow. Development with Xcode has become extremely slow. iOS has unusual and newly introduced quirks.
Highlight Apple's successes, but at the same time, acknowledge the problems and let's work on a way to improve it.
[doublepost=1512222276][/doublepost]Bring back... Avie Tevanian!

There’s a fine line between acknowledging problems and criticism for the sake of criticism. It’s also funny that you would bring up highlighting Apple’s successes, because I honestly can’t remember the last time I saw any of Apple’s accomplishments being recognised here, much less celebrated. They are either downplayed, or someone will find a way to turn it around and use it as evidence that Apple is further losing the plot.

Yes, this has been an awkward week for Apple in terms of software bugs. But it’s also a year where Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), in addition to updating 4 operating systems simultaneously. In addition to the iMac Pro later this month and the HomePod later next year.

This is the context I am talking about. So I don’t know what baseline you are using when a couple of software bugs somehow nullifies or obviates everything else Apple has done for the year.

Seriously, what happened to turn this place into a seething morass of toxicity and negativity? I remember coming here many moons ago when I got my first iMac to ask for help with the OS and the community was so helpful and upbeat. Then something changed and here we are today, reduced to this?!?

What gives?

 

[gnasher729]

It's April 1 right? Because how can this be real? I hope heads are rolling at Apple because iOS 11 has been riddled with bugs - simple things that were simply overlooked or not tested. Lazy times at HQ.

It's not April 1st, it's December 2nd. The problem doesn't happen on April 1st, only on December 2nd.

 

[neutralguy]

this is sad... i swear quality control is going down the drain, and its not just apple. not even within technology companies. this seems to be a trend for any corporation

This is what happens when you make the supply chain guy as CEO. You always need a guy who cares for the product.

 

[drewyboy]

Apple SW has been going down the hill for some time now, but this is embarrassing - are we back to the old windows wisdom - don’t upgrade a working system?

Yes. That's why my 2012 MBP hasn't touched Sierra, any of them and my iPhones are still rocking iOS10. Lack luster features laced with bugs. No thanks.

 

[gnasher729]

How are all these bugs turning up. Maybe not in this case but somethings should have been caught during beta testing. Makes me wonder if people are more interested in just having the latest iOS rather than looking for bugs and issues.

It doesn't turn up because it apparently only affects people on December 2nd or later. In QA, you might check if things go right on Jan 1st (year change), Feb. 29th, when daylight savings time changes and so on. But December 2nd? December 3rd?

That said, it seems it would be a good idea for Apple to have one of each phone model to run with the clock set two weeks ahead, so they might have caught the problem two week ago and fixed it before it affects users.

 

[drewyboy]

It's not April 1st, it's December 2nd. The problem doesn't happen on April 1st, only on December 2nd.

I still can't believe it took them 2 years to fix the daylight savings issue.
[doublepost=1512228712][/doublepost]

It doesn't turn up because it apparently only affects people on December 2nd or later. In QA, you might check if things go right on Jan 1st (year change), Feb. 29th, when daylight savings time changes and so on. But December 2nd? December 3rd?

That said, it seems it would be a good idea for Apple to have one of each phone model to run with the clock set two weeks ahead, so they might have caught the problem two week ago and fixed it before it affects users.

With their past issues of dates, they should be testing it. It's not that hard to setup an automated system to test for this type of stuff. We do it all the time at my work for our software that runs on our hardware. Does it take some time to run, yes but our stuff is mission critical for our customers and crap like this would be absolutely unacceptable.

 

[gnasher729]

Apple publicly admitted they have a problem with QC and have vowed to fix it. Clearly this latest bug is just an example that their problem won't be straightened out overnight. iOs 11.2 and the macOS security update were both released in almost record time so that's a good start to righting the wrong. Give them a chance folks.

I'll repeat this: The problem is not QA. The MacOS desaster (I won't call it a bug, it was a desaster) is not something that I would have expected anyone in QA to find. It's something that would have been prevented by (a) hiring developers who don't make changes to security critical features without telling someone competent, and (b) reviewing any changes made, and reviewing any changes to security critical features twice. It's not something that should have ever got as far as QA. Note that people who detected it didn't figure out the consequences for quite a while.

 

[idark77]

Well, that's different. Your original post stated, "we never forget". "we" as in the Apple customer community as a group generally forget.


The amount of "chance" I give a company is directly related to (A) how much of a premium I believe I pay for a product and (B) their corporate profits.

I extend a lot of grace for a young startup company scraping by to get product out the door at a reasonable price. I don't have a lot of grace for established companies who charge a premium for their product that result in them earning record-setting profits.

Ok now I change to: me and other people like me never forget.
Hope this time is the last. Bah...

 

[gnasher729]

If Steve were here, those engineers who let this through would have been told to fix the bug, to release the update and then to pack their stuff in order to be escorted from the premises.

I don't think so. For one, it doesn't make any sense. Either you escort someone from the premises, or you don't. If you escort them from the premises, you don't let them fix bugs first. And there is always the principle that "**** happens".

 

[MH01]

Apple publicly admitted they have a problem with QC and have vowed to fix it. Clearly this latest bug is just an example that their problem won't be straightened out overnight. iOs 11.2 and the macOS security update were both released in almost record time so that's a good start to righting the wrong. Give them a chance folks.

You are talking about Apple right ? Sounds like a small start up what struggles with funding for resourcing resulting in QC problems . Apple does not require us to "give them a chance" Apple needs to fix thier development processes to improve QC, it's not a quick fix, it's a process cultural shift of launching software of a certain quality and not launching software you think you can patch asap, Apple has shifted to the later
[doublepost=1512230475][/doublepost]

There’s a fine line between acknowledging problems and criticism for the sake of criticism. It’s also funny that you would bring up highlighting Apple’s successes, because I honestly can’t remember the last time I saw any of Apple’s accomplishments being recognised here, much less celebrated. They are either downplayed, or someone will find a way to turn it around and use it as evidence that Apple is further losing the plot.

Yes, this has been an awkward week for Apple in terms of software bugs. But it’s also a year where Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), in addition to updating 4 operating systems simultaneously. In addition to the iMac Pro later this month and the HomePod later next year.

This is the context I am talking about. So I don’t know what baseline you are using when a couple of software bugs somehow nullifies or obviates everything else Apple has done for the year.

Seriously, what happened to turn this place into a seething morass of toxicity and negativity? I remember coming here many moons ago when I got my first iMac to ask for help with the OS and the community was so helpful and upbeat. Then something changed and here we are today, reduced to this?!?

What gives?

I can answer that .

A £4K MacBook Pro and a £1350 iPhone - my patting apple on the back for releasing nice products has taken a back seat lately , cause I expect premium quality - software included - when Cook hikes the prices.

I do not accept price hikes, with poor quality - my value for money bar, is dropping fast - and as I can see others are also upset by this trend.

So please don't blame the punters paying more.... they have every right to expect more for higher prices.

Tl:tr - my MacBook Pro + iPhone = £5350 + .... this is not good enough .... venting ....

 

[IPPlanMan]

What haopened to “it just works”?

It left with Steve unfortunately.
[doublepost=1512230599][/doublepost]

This is what happens when you make the supply chain guy as CEO. You always need a guy who cares for the product.

Steve warned us.

 

[smacrumon]

There’s a fine line between acknowledging problems and criticism for the sake of criticism. It’s also funny that you would bring up highlighting Apple’s successes, because I honestly can’t remember the last time I saw any of Apple’s accomplishments being recognised here, much less celebrated. They are either downplayed, or someone will find a way to turn it around and use it as evidence that Apple is further losing the plot.

Yes, this has been an awkward week for Apple in terms of software bugs. But it’s also a year where Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), in addition to updating 4 operating systems simultaneously. In addition to the iMac Pro later this month and the HomePod later next year.

This is the context I am talking about. So I don’t know what baseline you are using when a couple of software bugs somehow nullifies or obviates everything else Apple has done for the year.

Seriously, what happened to turn this place into a seething morass of toxicity and negativity? I remember coming here many moons ago when I got my first iMac to ask for help with the OS and the community was so helpful and upbeat. Then something changed and here we are today, reduced to this?!?

What gives?

Maybe I could do more high fives, but I think that's unnecessary. The fact that I own parts of the Apple ecosystem is public support enough. I do prefer my commentary to be focused on what things could be done differently and better.

This is my point, if Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), then do it right, get them right, make sure they're right for public release. Test, test, test and test some more. Apple is slowly becoming the PC in the Mac and PC commercials that ran a decade ago I'm afraid. They've become too comfortable.

Also, the HomePod was announced for this year, but it's not happening now. Apple should never have announced HomePod until it was ready to ship the very day of announcement or a week later. Like they used to do. This whole announce things and not deliver by the due date is really sloppy. It's anti-climatic. It's disappointing. You have to agree with that.

Constructive criticisms are different to negativity and toxicity. For many years I observed the forums here before entering the territory, and for the most part, it is just as cutting than ever unfortunately.

 

[neliason]

As disconcerting as the recent Apple bugfest is, I wonder if problems are a consequence of increasingly complex code doing more while supporting the ever-more-fragmented iOS based products.

The complex code is legitimate. The devices are doing a lot and syncing across products. The fragmented products I don’t see as much. Apple still supports relatively few devices. The normally excellent interaction of the various devices is a complexity.

 

[iphonehype]

If Steve were here, those engineers who let this through would have been told to fix the bug, to release the update and then to pack their stuff in order to be escorted from the premises.

I miss Steve. Apple has fallen so much.

Apple has grown so much since Steve. The iPhone has grown so much since the iPhone. One little issue we look at the failures rather than how well Apple is doing. Apple Music? Watch? iPhone? HomePod? AirPods? MacBook? iMac Pro? Will miss Steve?

Let’s be greatful for the fact Apple is still number one in innovation, or, easily accessible innovation, consumer innovation. Or whatever it is.

 

[profmjh]

There’s a fine line between acknowledging problems and criticism for the sake of criticism. It’s also funny that you would bring up highlighting Apple’s successes, because I honestly can’t remember the last time I saw any of Apple’s accomplishments being recognised here, much less celebrated. They are either downplayed, or someone will find a way to turn it around and use it as evidence that Apple is further losing the plot.

Yes, this has been an awkward week for Apple in terms of software bugs. But it’s also a year where Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), in addition to updating 4 operating systems simultaneously. In addition to the iMac Pro later this month and the HomePod later next year.

This is the context I am talking about. So I don’t know what baseline you are using when a couple of software bugs somehow nullifies or obviates everything else Apple has done for the year.

Seriously, what happened to turn this place into a seething morass of toxicity and negativity? I remember coming here many moons ago when I got my first iMac to ask for help with the OS and the community was so helpful and upbeat. Then something changed and here we are today, reduced to this?!?

What gives?

Two things.

First, Apple products are hugely, hugely expensive. You pay a massive premium you expect perfection.

Second, Apple no longer seems to be joined up. Last year the iPhone 7 had no 3.5mm jack, yet AirPods took another two months to be released and even when they were delivery times were six weeks. This year the 8 and X have wireless charging yet there’s no Apple wireless charger. There’s not even a date for one. None of this screams competence.

 

[MH01]

Constructive criticisms are different to negativity and toxicity. For many years I observed the forums here before entering the territory, and for the most part, it is just as cutting than ever unfortunately.

I agree with this . Sadly many here don't understand what constructive criticism is , and that people can own and choose Apple while being unhappy about certain aspects . All products / companies have pros / cons , and This weeks issues are unacceptable .... for me ...

 

[harriska2]

[doublepost=1512221308][/doublepost]I got this fixed by resetting all settings from my IPad Pro and IPad mini at least for the moment.

Better not have! Just updated 3 machines, soon to be 4. The keyboard click didn’t get reset so I’m wondering what got reset for you?

 

[Letsi]

There’s a fine line between acknowledging problems and criticism for the sake of criticism. It’s also funny that you would bring up highlighting Apple’s successes, because I honestly can’t remember the last time I saw any of Apple’s accomplishments being recognized here, much less celebrated. They are either downplayed, or someone will find a way to turn it around and use it as evidence that Apple is further losing the plot.

Yes, this has been an awkward week for Apple in terms of software bugs. But it’s also a year where Apple refreshed a ton of hardware (iPads, iPhones, macs, Apple Watch), in addition to updating 4 operating systems simultaneously. In addition to the iMac Pro later this month and the HomePod later next year.

This is the context I am talking about. So I don’t know what baseline you are using when a couple of software bugs somehow nullifies or obviates everything else Apple has done for the year.

Seriously, what happened to turn this place into a seething morass of toxicity and negativity? I remember coming here many moons ago when I got my first iMac to ask for help with the OS and the community was so helpful and upbeat. Then something changed and here we are today, reduced to this?!?

What gives?

Personal question, did you encounter this bug in the first place before you made your initial comment?

Trying to google for a solution while your iPhone is re-springing every other minute is near impossible considering it resets whatever app you have running at the point of time. I was out the whole day alone when this bug happened and honestly, you can't do much with a mobile device that decides to reboot itself every other minute. I was about to give up and go to the local Applecare to understand if my battery's causing the issue.

All the usual method of resetting settings, hard reset and even data restore does nothing to alleviate the problem. It's only due to the fact that this bug was widespread enough to get coverage from my local media, that I found out about the workaround. Which non-tech-savvy person would have guessed intuitively that they need to turn off auto time-sync and rewind the date for this bug to stop activating? I thought the days of resetting the system clock to beat trialware evaluation periods were gone but what do I know...

For those saying Google would not have resolved such issues as promptly as Apple, let's just say that I've not seen an official GA release on my android devices from Google that bricks them... yet... Also, I'm paying the extra premium to Apple for that additional peace of mind which has been betrayed.

You should be facing the wrath of the irate users in Apple stores all over the world, especially those who are holding on to their premium iPhone Xs and it'll be a sight to see the reactions you get from them when you informed them that this bug is just a minor glitch in the overall iOS ecosystem.

 

[neliason]

How can Dec. 2 2017 cause a problem? What was special about this date? Y2K made sense because legacy code didn’t store dates in big enough registers. I’m really curious about what exactly the error was.