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

[iphonehype]

All the people that moan (inc me sometimes), do you moan in your personal life? Bills too high? Oil company are idiots for increase the price of gas / fuel? The light bul

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.

You know you created the expectation of perfect in your own mind? You know your understanding ot experience or whatever you call it of expert is created by you?

 

[robertvence]

No problems on my iPhone X, EST.

Going to sleep, chicken littles.

Depends on what apps you have installed. Not all apps triggered the bug. My iPhone X had the problem. Wife's 6S Plus (also running 11.1.2) did not. Very disturbing bug. Only 30 seconds between reboots. Finally found solution by turning off notifications (after a lot of reboots to get there). Had to turn off about 20 before I hit the right one. Also reset the date to December 1. Upgraded to 11.2. After update, Face ID had to be reset, but working OK now.

 

[luddx]

this is microsoft-tier malfunction......... wow apple.

 

[canny]

Cook has been reducing QA at Apple over the last few years. There’s barely a dozen people left.

I know people who work at, and who have interviewed at Apple. Their QA and testing is very demoralised. Especially compared to the likes of Microsoft and Google.

Basically, Tim doesn’t care about the fundamental qualities that Apple once had. It’s just tech gimmicks and his own narcissism that matter.

I doubt anyone will even be fired. They’re so short-staffed that they couldn’t afford to lose anyone.

 

[nt5672]

why do I have a feeling that 30% commenting in this post are trolls and does not have any ios device at all??? I did not experience this bug - luckily me - because i only have a hand full of apps and most of them have notifications set to OFF. I hope apple will release 11.1.3 (if there will be one) or 11.2 (since 11.2 seems to be unaffected) as soon as possible.

Yep, if you use Apple equipment the way Apple expects, as a teenager would, then the chances are you won't see any of the bugs. Teenagers are not exactly hard to please. If the device has bling and is popular that is all that matters.
[doublepost=1512253428][/doublepost]

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

Sorry, but that should be corrected to read, "You always need a guy who cares for and understands the product". I don't think there is any doubt that Cook cares about Apple's products, they have made him a multimillionaire, he just does not understand what it fundamentally takes to force a company to turn out great products day after day.

 

[Sedulous]

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.

I honestly have no evidence, that is why it was “I wonder if”. But I do remember when there was basically one version of iOS. Now there are versions for iPads, iPad mini, iPad Pro, iPhones, and all the various iterations of those devices with various display sizes, technologies, with/without touchID, faceID, dozens of different cameras, Intel/Qualcomm chips, and on and on. All those different iterations must make things more complex to support. Let's also not forget watchOS and tvOS too.

One of the things I used to like about Apple was the streamlined product line. It was efficient and allowed Apple to focus. Consumer / Prosumer. Now it seems like their products are a confused mess... both hardware-wise (i.e. iMac Pro... why!?!) and also software (let's gut our professional software then add stupid bugs to it instead).

If I were in charge, I'd get back to a streamlined product line with basically a divide between consumer and prosumer (think: iPad/iPad Pro, iPhone/iPhone Pro, Macbook/Macbook Pro, Macmini/Mac Pro).

 

[HiRez]

Aren't all these bugs what all the test processes, then all the private betas, then all the public betas are for? Why are so many major bugs still appearing in what should be the release version, and not even the first one? This is embarrassing.

This is not a minor bug by the way, what if you have your alarm set for an interview or meeting or whatever? I know phones are complex these days, but not even being able to count on the clock—the clock!— is pretty pathetic.

Anyway, why would 12:15 on December 2 trigger anything at all? Seems like such a random date/time. Must be something like it overflows 32 bits of milliseconds since January 1, 1970 or whatever.

 

[cfurlin]

I see the outrage machine has been turned up to 11 again today. /facepalm

 

[The Game 161]

luckily this bug didn't hit me but at 12.15am i would be asleep anyway

 

[gnasher729]

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.

I'm very curious as well. At one company we had a bug that crashed things on February 2nd, 2000. The bug itself was totally brain damaged. The reason why it did strike on that day was because it was the first day in the history of computing that didn't contain the digit "1" (the last day before the history of computing without a "1" was September 30th, 999).

Microsoft had a bug that did strike on a 29th of February. The root cause was that their code calculated the date "one year after today", and if it's the 29th of February today, then the next year won't have a February 29th.

 

[alembic]

Cook has been reducing QA at Apple over the last few years. There’s barely a dozen people left.

I know people who work at, and who have interviewed at Apple.
...
They’re so short-staffed that they couldn’t afford to lose anyone.

Assuming the remaining dozen or so people cover both macOS and iOS, it seems shortsighted considering the string of embarrassing bugs that have bit them recently. It also may explain why Server has continued to receive poor ratings since the group doesn't have the bandwidth to address long standing issues on a marginal product.

Apple's software engineering group certainly understands the value of proper QA. Not sure Tim Cook does though.

 

[neliason]

I'm very curious as well. At one company we had a bug that crashed things on February 2nd, 2000. The bug itself was totally brain damaged. The reason why it did strike on that day was because it was the first day in the history of computing that didn't contain the digit "1" (the last day before the history of computing without a "1" was September 30th, 999).

Microsoft had a bug that did strike on a 29th of February. The root cause was that their code calculated the date "one year after today", and if it's the 29th of February today, then the next year won't have a February 29th.

That was a crazy bug relying on a one in a date!

 

[Abazigal]

I honestly have no evidence, that is why it was “I wonder if”. But I do remember when there was basically one version of iOS. Now there are versions for iPads, iPad mini, iPad Pro, iPhones, and all the various iterations of those devices with various display sizes, technologies, with/without touchID, faceID, dozens of different cameras, Intel/Qualcomm chips, and on and on. All those different iterations must make things more complex to support. Let's also not forget watchOS and tvOS too.

One of the things I used to like about Apple was the streamlined product line. It was efficient and allowed Apple to focus. Consumer / Prosumer. Now it seems like their products are a confused mess... both hardware-wise (i.e. iMac Pro... why!?!) and also software (let's gut our professional software then add stupid bugs to it instead).

If I were in charge, I'd get back to a streamlined product line with basically a divide between consumer and prosumer (think: iPad/iPad Pro, iPhone/iPhone Pro, Macbook/Macbook Pro, Macmini/Mac Pro).

I agree with you fundamentally, but I suspect that Apple personally prefers the iMac over the Mac Pro / Mac mini. Maybe due to higher margins? Perhaps it’s easier to manufacture an iMac variant than dedicate an assembly line to a completely new product? They just prefer the concept better? Hence the iMac Pro to serve as a replacement for the Mac Pro.

I would drop the MacBook altogether as well, while we are at it.

 

[Burger Thing]

I agree with you fundamentally, but I suspect that Apple personally prefers the iMac over the Mac Pro / Mac mini. Maybe due to higher margins? Perhaps it’s easier to manufacture an iMac variant than dedicate an assembly line to a completely new product? They just prefer the concept better? Hence the iMac Pro to serve as a replacement for the Mac Pro.

I would drop the MacBook altogether as well, while we are at it.

I.T‘s clear, that Apple has lost the plot understanding what the Pro Community wants or needs. I.T‘s also quite evident in your posts, that you don’t really have an understanding either.

The Pro Community would probably light up candles united in various churches around the world, if Apple would just warm up the assembly lines of the late Cheesegrater MP and stuff I.T with 2018 specs. Not exactly rocket science. Maybe throw in a decently specced non Gimmick MBP 17“, too.

What a shame that the richest company in the world can not cater for some non-mainstream models.

 

[Abazigal]

I.T‘s clear, that Apple has lost the plot understanding what the Pro Community wants or needs. I.T‘s also quite evident in your posts, that you don’t really have an understanding either.

The Pro Community would probably light up candles united in various churches around the world, if Apple would just warm up the assembly lines of the late Cheesegrater MP and stuff I.T with 2018 specs. Not exactly rocket science. Maybe throw in a decently specced non Gimmick MBP 17“, too.

What a shame that the richest company in the world can not cater for some non-mainstream models.

I would argue that it is precisely because of Apple’s size and scale that it likely no longer makes sense for them to cater to an increasingly niche crowd. Both in terms of resources devoted to updating the devices, to producing and supporting them. There’s just no money to be made from a hypothetical Mac Pro line which is going to be purchased only by an overwhelmingly minority of Mac users.

Can Apple support the Pro Mac community? It certainly has the resources to do so. Should Apple continue to do so? You will find that the argument isn’t as clear cut and straightforward as you might imagine, and there are more factors at play here than just “your needs”.

 

[paulmackay]

A date-related bug in iOS 11.1.2 appears to be causing iPhones and iPads to continually crash or respring when time-based local notifications are received after 12:15 a.m. on December 2, according to reports on Twitter and reddit.

The problem seems to be tied to local notifications received from apps that offer daily or repeat reminders. For example, meditation app Headspace, one of the affected apps, sends daily reminders to users to encourage them to take some time to meditate. Any app using local (as in not pushed from a remote server) notifications that repeat will cause a crash.

​

On reddit, users have had some success fixing the issue by disabling notifications and turning off background app refresh, while Apple's support staff appears to be recommending a manual date change to a time before the problem occurred as a temporarily solution. Reinstalling apps and restarting does not fix the issue. The problem looks like it's limited to devices running iOS 11.1.2 -- devices on the current iOS 11.2 beta aren't affected.

Apple Stores in Australia, where it is late afternoon on December 2, are reportedly being inundated with support requests from customers who are experiencing the issue.

​

Apple will undoubtedly fix this problem quickly through an iOS update, but as people wake up on December 2 in the United States and other countries throughout the world, there's likely to be quite a lot of confusion when devices begin inexplicably respringing over and over again.

If you're experiencing continual crashing, the first thing to try is disabling notifications for apps that send regular reminders. It can, however, be difficult to tell which apps are responsible, so a secondary solution is to set the date on your iPhone to before December 2 as you await a fix from Apple.

If you aren't experiencing any crashes, there's no need to turn off notifications or adjust the date on your device.

Update: Apple has released iOS 11.2 to fix this problem, along with an accompanying support document outlining steps to take if you're experiencing crashes. Apple recommends turning off notifications and then installing the update.


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

[doublepost=1512271219][/doublepost]how hard is this. every time I open the open to do the up date it re springs and locks itself :-(

 

[Amazing Iceman]

Hah! it started happening to my iPhone SE. I ended up doing a Reset All Settings and then it worked.
I had to stay awake until 3:00 am.. Not amusing!

 

[PizzaBoxStyle]

Software development quality was going down since the Agile development methodology is on an upward trend. They just keep want to pushing things (****) to production, even there has no enough time to think about the total solution / doing better coding and performing well testing. i don't know why this methodology become famous but seems it ruling the development world.

Agreed about the overall trend.

I saw this the other day:

https://twitter.com/Real_CSS_Tricks/status/934904607339372544

Too funny. I think there's some truth to it.

You may already know, but... Agile is really more about loosely defining the requirements so discovery doesn't have to be done all up front. It's also about chunking the work into three-week (or so) work periods, then sending for feedback. Also depends on if the project is a new build, or in maintenance.

It's not about haphazardly pushing code into production. That's the whole "move fast and break things" mantra. It seems to have been where Apple software has ended up, probably to no fault of the developers in the trenches. We may truly be in a Scully 2.0 era.

 

[dumastudetto]

What a buggy mess. Android doesn't have these problems.

Android has many other problems. Probably 90% of Android phones are running insecure software that will never be patched.

 

[PizzaBoxStyle]

I would argue that it is precisely because of Apple’s size and scale that it likely no longer makes sense for them to cater to an increasingly niche crowd. Both in terms of resources devoted to updating the devices, to producing and supporting them. There’s just no money to be made from a hypothetical Mac Pro line which is going to be purchased only by an overwhelmingly minority of Mac users.

Can Apple support the Pro Mac community? It certainly has the resources to do so. Should Apple continue to do so? You will find that the argument isn’t as clear cut and straightforward as you might imagine, and there are more factors at play here than just “your needs”.

Maybe now's the time when Apple lets us officially install macOS on any old Wintel box.

They can still make a simple machine or two for those who don't want to bother, but let us install macOS on whatever monster hardware we want to.

 

[Abazigal]

Maybe now's the time when Apple lets us officially install macOS on any old Wintel box.

They can still make a simple machine or two for those who don't want to bother, but let us install macOS on whatever monster hardware we want to.

Well, therein lies the downside of a closed ecosystem. It has always been Apple’s vision of computing you are subscribed to, never your own. If you are lucky, it happens to match what you need (which is basically me at this point). Else, you will just have to cobble together what’s left and make do the best you can.

 

[canesalato]

iMac Pro... why!?!

Money

 

[croco_dile]

No issue on any of my iOS devices running the iOS 11.1.2...

scaremongoring much!
[doublepost=1512305235][/doublepost]

Samoa

No Apple User on the little island?

 

[TheNorthWaves]

All of these constant bugs and unnecessary functionality changes (not just in the past couple of months, but I've noticed a decline in the past year or so) are making me consider something that used to be unthinkable. Next phone upgrade cycle I will be looking at Android phones alongside iOS. I've been a die hard Apple guy for a decade. I can't be the only person thinking this. When Apple starts to notice this trend in 3 or 4 years just reference my post as the reason

 

[muthuece12]

A date-related bug in iOS 11.1.2 appears to be causing iPhones and iPads to continually crash or respring when time-based local notifications are received after 12:15 a.m. on December 2, according to reports on Twitter and reddit.

The problem seems to be tied to local notifications received from apps that offer daily or repeat reminders. For example, meditation app Headspace, one of the affected apps, sends daily reminders to users to encourage them to take some time to meditate. Any app using local (as in not pushed from a remote server) notifications that repeat will cause a crash.

​

On reddit, users have had some success fixing the issue by disabling notifications and turning off background app refresh, while Apple's support staff appears to be recommending a manual date change to a time before the problem occurred as a temporarily solution. Reinstalling apps and restarting does not fix the issue. The problem looks like it's limited to devices running iOS 11.1.2 -- devices on the current iOS 11.2 beta aren't affected.

Apple Stores in Australia, where it is late afternoon on December 2, are reportedly being inundated with support requests from customers who are experiencing the issue.

​

Apple will undoubtedly fix this problem quickly through an iOS update, but as people wake up on December 2 in the United States and other countries throughout the world, there's likely to be quite a lot of confusion when devices begin inexplicably respringing over and over again.

If you're experiencing continual crashing, the first thing to try is disabling notifications for apps that send regular reminders. It can, however, be difficult to tell which apps are responsible, so a secondary solution is to set the date on your iPhone to before December 2 as you await a fix from Apple.

If you aren't experiencing any crashes, there's no need to turn off notifications or adjust the date on your device.

Update: Apple has released iOS 11.2 to fix this problem, along with an accompanying support document outlining steps to take if you're experiencing crashes. Apple recommends turning off notifications and then installing the update.


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

[doublepost=1512314077][/doublepost]Hi Everyone,
My Mobile (IPhone 7) Running 11.1.1 not 11.1.2 also only started to crash Dec 3 Not Dec 2. Do you have any ideas?. I know solution. but i would like to know the reason. Why Apple making such a blender mistake in date again and again.