Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
They should make it so you can just update the app without requiring an iOS update that may introduce other issues.
 
Ironically my messages app crashed on my iPhone X this morning. This problem not related. I was about to text a co worker and the app just crashed on its own.
 
Remind me why we’re jumping from 11.2.2 to 11.2.5 ..?

I'm sure there's an internal reason, probably a consolidation of patches triggered by a delay in 11.2.2, resulting in changes that were expected to be 11.2.3 or 11.2.4 being rolled into it. It's a hell of a lot easier to not have to say things like "this was patched for 11.2.4, but we ended up shipping it in 11.2.2" and "this was patched in 11.2.3, I mean the second version of 11.2.3 not the one we burned" But from our perspective? 1.2.5 is greater than 1.2.2. Great!
[doublepost=1516311585][/doublepost]
Here’s hoping they fix the other prolific bug of messages freezing or crashing a couple times per day on days when the sky is blue

Huh, I've never seen Messages crash before. iBooks? All the time.
[doublepost=1516311656][/doublepost]
Apple just goes from one patch to another these days...

There are two ways to handle bugs:

1. Don't fix them, beyond the first round of most urgent bugs and maybe one release every few months after that. (This has been Apple in the past.)
2. Fix them and release them in a timely fashion. (Apple lately.)
 
  • Like
Reactions: centauratlas
Thousands....Apple and others, doing too many changes in too short a time frame. Each year it gets worse. The problems the sloppy coding cause are a headache enough, then add the hours of users time to implement the patches. I have 7 IOS and Mac OS products. Updating just these few costs me at a minimum 1 tp 2 hours each time. Multiply that times the number of Apple products worldwide, a significant cost in loss of productivity in time and a Monies. Apple needs to be more sensitive to our time and costs.


Amazing how people can whine about anything. Sorry. Frequent updates is a good thing.

sigh
 
Remind me why we’re jumping from 11.2.2 to 11.2.5 ..?

Because 11.2.5 is a bigger step. (It may include AirPlay 2.)
[doublepost=1516311917][/doublepost]
That can also depend on where the actual issue is and where the actual fix for it is.

Yup. Presumably, they don’t fix Messages, but rather improve text rendering altogether. Plus side: all apps benefit.
 
the hours of users time to implement the patches. I have 7 IOS and Mac OS products. Updating just these few costs me at a minimum 1 tp 2 hours each time.

iOS devices update automatically at night. All you have to do is enter the passcode in the evening, then again after the reboot the next morning.

I don’t see the issue.
 
  • Like
Reactions: s15119
Apple just goes from one patch to another these days...


No different than any other time. There have always been people hacking ALL systems to try to find weakness and the vendor patching those hacks. This has been the case for every operating system since the earliest computers. Has noting to do with "Apple" or "these days - it's every computer vendor from forever.
 
  • Like
Reactions: spinnyd
Amazing how people can whine about anything. Sorry. Frequent updates is a good thing.

sigh
My point, I buy Apple products to use them, they just work, and willing to pay a significant premium, so I am using rather then fixing. If I want to continue spending about 25 hours, so far on IOS 11, might as well buy something that will save me thousands of dollars and be happy frequently updating. I expect more from Apple, willing to pay more, and when I buy premium products I have higher expectations. That my friend is Not whining.
[doublepost=1516319132][/doublepost]
iOS devices update automatically at night. All you have to do is enter the passcode in the evening, then again after the reboot the next morning.

I don’t see the issue.
Lots of reasons that I want to control the time when my IOS device bricks. Waking up in the morning to a bricked iPhone, even once, not a good start. Just one example. Additionally, all the problems that one finds after the upgrades, very time consuming. IOS11, so many little annoying things that worked, then do not, then work again. As noted earlier, I pay a premium for Apple products, as such my expectations are set higher. If Apple no different then let’s say Android Devices, why should anyone pay a premium, was my point.
 
Last edited:
Remind me why we’re jumping from 11.2.2 to 11.2.5 ..?

Honest question: what happened to 11.2.3 and 11.2.4? My iPhone 7 is “up to date” running 11.2.2.
Nothing really happened to those. At some point Apple had some fixes/changes they wanted to be in an upcoming bug fix release that they wanted to test with developer and public betas so they designated that release as iOS 11.2.5 leaving some room for potential bug fix releases that might need to be released prior to that (due to some security issues or something else important/sensitive that can't really wait).
 
  • Like
Reactions: BornAgainApple
My point, I buy Apple products to use them, they just work, and willing to pay a significant premium, so I am using rather then fixing. If I want to continue spending about 25 hours, so far on IOS 11, might as well buy something that will save me thousands of dollars and be happy frequently updating. I expect more from Apple, willing to pay more, and when I buy premium products I have higher expectations. That my friend is Not whining.
[doublepost=1516319132][/doublepost].

Easy enough. Go buy something you like. I have no idea why it takes you so long to start an update. But, hey. Maybe Android will "just work" for you. Good luck. I'll stick with great software that is updated regularly.
 
I'm sure there's an internal reason, probably a consolidation of patches triggered by a delay in 11.2.2, resulting in changes that were expected to be 11.2.3 or 11.2.4 being rolled into it. It's a hell of a lot easier to not have to say things like "this was patched for 11.2.4, but we ended up shipping it in 11.2.2" and "this was patched in 11.2.3, I mean the second version of 11.2.3 not the one we burned" But from our perspective? 1.2.5 is greater than 1.2.2. Great!
[doublepost=1516311585][/doublepost]

Huh, I've never seen Messages crash before. iBooks? All the time.
[doublepost=1516311656][/doublepost]

There are two ways to handle bugs:

1. Don't fix them, beyond the first round of most urgent bugs and maybe one release every few months after that. (This has been Apple in the past.)
2. Fix them and release them in a timely fashion. (Apple lately.)
Yesterday and today I was talking to a potential client and my iPhone crashed both times. I kind of deserved it though; I neglected to use the SE running 10.3.3 that I bought for performing critical tasks, naively thinking I could depend on my iPhone X. I’d take a trip down to the Genius Bar to try and rectify this, but Apple has decided that Today at Apple is more critical to the long term success of the company than maintaining its formerly legendary attention to detail and customer service.
 
That can also depend on where the actual issue is and where the actual fix for it is.

I expect they’ll re-architect things so they can update preinstalled apps independent of the OS before too much longer. I think they realize the problem they are having maintaining the monolithic release schedule and quality.
 
I expect they’ll re-architect things so they can update preinstalled apps independent of the OS before too much longer. I think they realize the problem they are having maintaining the monolithic release schedule and quality.
It's quite possible something like that would happen. That said, even with that, if there are some issues here or there some of them might still require an OS level update rather than an app level one.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.