Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I fully agree. In the past, for a couple of years, I would upgrade to a new OS (on my Mac and iPhone) only a couple days before the latest OS would be released. So I’d be on one of the final versions of the previous generation OS. That strategy served me well for those couple of years because I’d be on a stable OS without many bugs.

I regret upgrading to macOS 13 Ventura and iOS 16. With both of those, I waited until the x.3 version was released to upgrade. However, they are both still very buggy, even now at macOS 13.5 and iOS 16.6. Those are almost the final versions, yet they are still very buggy.

I’m not sure what to do. Should I upgrade to macOS 14.2 and iOS 17.2 whenever those get released, or should I stick with the latest versions one of what I’m currently running? I’d appreciate any feedback on that.

There’s one thing I do know: if I were on the latest versions of macOS 12 and iOS 15, I would never upgrade to macOS 13 and iOS 16, and instead just wait until fall of next year to upgrade to the most mature versions of macOS 14 and iOS 17 a couple of days before their successors are released.
Interestingly, Ventura has been really solid for me minus this latest bug. iOS on the other hand 😑
 
  • Wow
Reactions: Pinkyyy 💜🍎
They get adding more bugs for all bugs fixing updates. Come on Apple, what a deception! I miss the good'old Snow Leopard days.
Exactly. My Mac when I switch between users frequently ends up not being able to open files with a double click. macOS is an absolute joke. I also initialised it and after a week I had the same issue. I have basically no software on it, just MS Office. M2 air, I am not using a 128k Macintosh, I would expect this crap to work decently. My next laptop won't be a Mac. They have a bunch of idiots running the software department.
 
How do you handle security fixes/patches? Having a feature not work properly is better than having a insecure system?
Ahh yeah “security fixes/patches”, as if those people would prefer works Being interrupted because of a broken system than having an “insecure” system.
Just wait until Apple releases security updates that bricks the system. “But, but my system now is up to date!”
 
I can't understand why a company the size of Apple doesn't allocate more resources to stay on top of things like this. And before anyone says 'that's not how software development works', please... there's no reason why an automated system wouldn't have picked this up.

Sheer sloppiness. And ultimately, greed.
 
What gets me about stuff like this is why beta testers didn’t pick this up. Apple releases both developer and public betas. You’d think somebody would have reported back.

There are a lot of posts on these forums from users bragging about how they are running the latest beta releases. Did any of you pick this up or do you just run betas for the heck of it?
Apple throws beta software to the crowd because they can’t be bothered to hire proper QA and an army of real-world testers who knows what they are doing.
I mean, if they want, they can start charging for macOS again and pay people using beta software to find bugs.
 
I can't understand why a company the size of Apple doesn't allocate more resources to stay on top of things like this. And before anyone says 'that's not how software development works', please... there's no reason why an automated system wouldn't have picked this up.

Sheer sloppiness. And ultimately, greed.
All in the name of saving costs and maximising shareholder value At the cost of everything else. Otherwise, why let macOS be free of charge?
 
All in the name of saving costs and maximising shareholder value At the cost of everything else. Otherwise, why let macOS be free of charge?
Perhaps that's what's needed: charge a modest fee for the major updates (which, let's be honest, aren't necessarily needed every year) and keep the minor updates free. Although I admit paying Apple even more money does make me recoil somewhat. You'd hope the cost of keeping macOS free was baked into the premium price they charge for their hardware.
 
Once upon a time I would have run a macOS software update in the middle of a work day without thinking twice.

These days if I'm working on anything at all, I end up delaying updates for weeks or months. I can't just tolerate Apple's sloppiness and lack of attention today. Too disruptive to the workflow.
Update fatigue is very real! Too many modern software updates happen too frequently and not well tested
 
  • Like
Reactions: Pinkyyy 💜🍎
Aaaaaaaand this is why I don't install macOS Betas anymore. The production releases are buggy enough as it is. I don't need more headaches.
 
  • Like
Reactions: Pinkyyy 💜🍎
Pretty funny people expecting 100.0% perfection 100.0% of the time.
On a forum like this one it’s more about bashing Apple than expecting perfection. Operating systems like macOS or Windows, or Linux will always be full of bugs, most go unnoticed by users, not many will be showstoppers. The code is so complex that bugs simply have to exist.
 
most go unnoticed by users, not many will be showstoppers. The code is so complex that bugs simply have to exist.
Are you f---ng kidding me? I noticed this bug within the first 20 minutes of using 13.5, because the weather data wasn't loading in Outlook. Very easy to find. In fact, to "discover" this elusive, rare bug all one of the devs or testers (if they even exist?) would have needed to do was literally just OPEN the Settings > Privacy > Location section. That's it. The fact they made obvious under the hood changes to this mechanism and didn't bother to even open the related UI that controls it shows how sloppy and disjointed macOS development has become under Cook and Federighi.
 
As a software developer, I expect bugs. As a software developer, I don't expect bugs as egregious as this one. It's not that there are bugs, it's what these particular kinds of bugs reveal about Apple's software development incompetence.

There was an seemingly inconsequential bug in Ventura a while ago. There was a thread on these forums, but it didn't get that much attention. If you turned on stealth mode in System Settings, it showed as being turned on. But if you came back to it later, it showed that it really hadn't been turned on.

That bug was trivial to catch during testing - especially since System Settings was a brand new application which was getting plenty of developer attention. It had a monumental impact to users on insecure networks who tried to take precautions. It was almost impossible for a user to notice. That level of incompetence erodes trust.

If you just take a birds-eye view and see a reasonably nice OS with some bugs (all software has bugs), then you'll draw a rosy conclusion. If you think about particular bugs and what they imply - not so rosy.
 
And this is why I keep delaying my upgrades. Even when Apple software reaches GM, it’s still a beta for quite some time and that’s usually until the next release.
13.5 is on the back shelf now. Hey Apple, fix this pronto. What I mean is I am on 13.5 and didn't notice it at all. Ugh.
 
Last edited:
FAAAAACCCCCCKKKK!
 

Attachments

  • Location Bug.png
    Location Bug.png
    28.2 KB · Views: 74
  • Sad
Reactions: Pinkyyy 💜🍎
As a software developer, I expect bugs. As a software developer, I don't expect bugs as egregious as this one. It's not that there are bugs, it's what these particular kinds of bugs reveal about Apple's software development incompetence.

There was an seemingly inconsequential bug in Ventura a while ago. There was a thread on these forums, but it didn't get that much attention. If you turned on stealth mode in System Settings, it showed as being turned on. But if you came back to it later, it showed that it really hadn't been turned on.

That bug was trivial to catch during testing - especially since System Settings was a brand new application which was getting plenty of developer attention. It had a monumental impact to users on insecure networks who tried to take precautions. It was almost impossible for a user to notice. That level of incompetence erodes trust.

If you just take a birds-eye view and see a reasonably nice OS with some bugs (all software has bugs), then you'll draw a rosy conclusion. If you think about particular bugs and what they imply - not so rosy.
And the change (for better or for worse) ought to have had an alert that things were updated/changed. It's serious. So now set my VPN to Chile?
 
There was at least one other major bug introduced with this update meaning App Store notifications aren't working either. As you say, this truly is a train wreck. Sadly we'll never see any sort of explanation or reassurance that policies have changed to ensure this doesn't happen again. We just have to hope it'll eventually be fixed and that Sonoma (for those able to update to it) won't be subject to the same blunders. Not very confidence-inspiring...
I know it's impossible to "ensure" 100% "this won't happen again" however but whether it's a talent shortfall or cost-cutting primacy, it shows that the MacOS team has lost a lot of institutional memory.
 
Currently, but Big Sur come this late Sept/Oct will fall off the well supported three most recent MacOS's. That is why Safari 17 is now being made available only to Monterey and Ventura, not Big Sur which will only be getting occasional patches in the near future. ;)
And when that happens, guess what? I will upgrade to Monterrey on this spare Mac I have.
 
  • Like
Reactions: Pinkyyy 💜🍎
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.