Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.



A date-related bug in iOS 11.1.2 appears to be causing iPhones 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.

crashloopios11-800x600.jpg

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.

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

Tomorrow is going to be a long day for Apple support staff....yikes!
 
  • Like
Reactions: robmorgan78
Gone past 5pm in Sydney, Australia, iOS 11.1.2 on iPhone X. Didn’t even know about this bug till I read this. No issue here.
 
  • Like
Reactions: johnnygee
Yikes...

What about the Reminders app... I have some weekly reminders set up there..
 
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.

Though I believe there is some truth to the above, this issue seems to be more a core function that should be the same across all devices.

Not surprised: the "new and improved" (ha!) Notification center has been real wonky for me. Apple too focused on change for change's sake, imo.
 
I usually don’t receive notifications late at night so I won’t know until tomorrow. As far as I know I don’t receive repeating notifications that are identical and occur at the same time everyday (if that’s the issue here). I guess one example would be a reminder notification to take your pills at the same time each day. It has the potential to be a very “interesting” day today if this really blows up. I’m just curious why it’s Dec. 2?
 
To quote Apple „we dont think of the price. We think of the great value and user experience we provide to our customers“

hahahaha, another week another bug on iOS 11. it seems like it is saver to use betas than final releases in Apples case nowadays. Sad

When Apple comes out with a statement, I’ll believe the panic.

https://www.apple.com/support/systemstatus/

Y2K all over again.

Post makes no sense whatsoever
 
The bug is described as local time-based, so why wouldn’t this affect iCould Reminders and iCloud Calendar on Apple’s servers?
It seems like it's related to date/time, but also to local notifications, as in those coming from within apps on devices themselves, as opposed to those being pushed remotely.
 
...because it affects iPhones not servers? it's causing iPhones to crash not services?

please tell me that this isn't really going that far over your head?

I’m well aware of the differences between server and local notifications. Apparently, my original post was too vague, so I’ll try again.

These reports are sourced from Twitter and reddit. When Apple confirms this, then it will be something to take notice.

In the meantime, I’m not going to panic in the streets like my iPhone is going to melt or think about how I’ll get through the rest of my life without Waterminder notifications.
 
Hit me last night, in a bar of all places. I briefly wondered whether I may have dropped it.

Anyway after seeing this story I tried the date reset which worked but I couldn't access WhatsApp. So I have just turned off all notifications and set the date back to auto. That worked, stopped resetting and I can access all my apps.
 
  • Like
Reactions: rgarjr
No issues on iPhone X runnning affected software here...

Some tech guys in Cupertino are going to work tired right now in their PJs.
 
This is the worst iPhone bug ever.. my iPhone SE is completely unusable, the respringing thing cut off every function ..the solution is to set yesterday date, I’ve done , it’s the only way to use my iPhone .. but this is ridiculously disturbing and distorting my calendar, events, emails, messages, calls, etc.., everything keep trace of time.
 
  • Like
Reactions: Retrostarscream
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.