Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I guess somebody should double down on quality very soon (probably not the same people who tried to avoid leaks though).
 
  • Like
Reactions: NaOH
wow! What did I wake up too! How do you turn back time on the iPhoen X? UK!

Woke up had a coffee figured it out
Cherfs
 
Last edited:
While I agree that some here tend to engage in melodrama, it serves a purpose... to blow off steam, an emotional release so that when the bug is fixed they can accept it and move on...


If past experience is any indication of future performance then you are wrong. People WILL forget, or at least remember but not to the point of influencing their purchasing decision.

WWDC will roll around next year and the people who "won't forget" will salivate in anticipation of the next big thing from Apple. And so it goes.

I don’t forget !
 
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.
 
Last edited:
I don’t forget !
Well, that's different. Your original post stated, "we never forget". "we" as in the Apple customer community as a group generally forget.

Apple publicly admitted they have a problem with QC and how 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.
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.
 
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.

I can only suggest you purchase another company's products then if they don't meet your expectations.
 
Wow, you guys are being way too dramatic about this.
I'd rather see a class suit action against Apple to implement the right to stay on a stable and proven iOS version on a permanent basis. It is lunatic how they can put down half of the world.
(leaving you the right to play down and apologize every major lockdown and find out what's more stable: beta's or new releases)
 
Can’t handle the heat I guess

Yeah Captain Obvious, If you didn't point out that past bug in HS I wouldn't had found about it :rolleyes:

Reminds me of when Microsoft locked out a few million users out of their official licensing rights because of some remote activation algorithm gone bad, which wasn't fixed overnight btw.

Either way, you are free to choose which OS you prefer to do your job, but NEVER to .1-3 updates on your main working machine. Ever. A Mac is not an iPhone, even if it looks pretty.
 



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.

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.

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=1512221308][/doublepost]I got this fixed by resetting all settings from my IPad Pro and IPad mini at least for the moment.
 
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.
 
That’s like saying your kid ought to be spanked for scoring only 98 on a test instead of 100.

Mistakes were made and will be rectified and life goes on.
Abazigal, a device that is crashing over and over is <50 / 100. It is a fail.
It's best if we make an honest and frank assessment of the issue, not glaze over it.
This is really poor form from Apple. The Apple company used to stand for perfection, but too many issues are slipping through, too many times has the ball been dropped. This includes buggy system software all the way to buggy early announcements of new products that fail to be delivered until many months later.
The lack of simplicity and professionalism of the Apple company is beginning to become embarrassing.
 
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.
 
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!
 
Last edited by a moderator:
  • Like
Reactions: nt5672
It’s 9:30PM on the 2nd of December here in Aus and there is an update available to download to fix the issue. That simply would not happen for android.

You never know. But then again, there never has any need to test it. Just sayin'.
 
I spent an hour trying to troubleshoot this before coming to Macrumors - figured I had another busted iPhone X :(

Any reason why iOS doesn't have an option to temporarily turn off all notifications? Would be handy for presentations from your device too.
 
What if you were in the middle of the Sahara desert and didn't know about the bug and had no way of updating?
Exactly. Many here, like me, are proud nerds who understand system software. But...
For the average user, they will unlikely know what is going on. And when the device is constantly crashing, the ability to discover what the solution is will be even more difficult.
Apple devices and the software should be "ease of use". Not constant updates to fix poorly written software.
Not a good look for Apple.
Stop beta testing on the wider public Apple. Test more internally before releasing to the public.
[doublepost=1512223051][/doublepost]Bring back... Avie Tevanian!
 
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.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.