Yeah I read his post, it's all bs from him despite he has like thousand of points lol. Sometime he's just full of himself.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Ventura 13.5 Breaks Location Services Permissions for Apps
- Thread starter MacRumors
- Start date
- Sort by reaction score
I am so glad that this is receiving the attention that it deserves. Perhaps Apple has been preoccupied with Sonoma. Yet not doing anything about this is just not right. Hopefully finally a software update may pear by next Tuesday. Or it may not…
If you contact Apple, it’s always just you!
I upgraded my iPhone X to 16.5 recently and subsequently 16.6 and its been smooth so far. Have been wanting to take advantage of the Apple Savings.
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.
It was reported during the 13.5 beta testing (at least once), I know that for a fact.
Last edited:
I am not so sure I believe "dedicated QA teams". I think Cook, in order to produce profits and goose his shares has cut QA to the bone. Nothing else really explains the major software bugs that have occurred recently across all teams.
I would not be surprised to learn that each development team is responsible for their own QA. After all Cook is a bean counter, not a technologist.
Gotta get marketing away from the development team. Since they started pushing product out based on college year starts, the quality of hardware and software released has gone downhill dramatically.
Are you saying youre goig to stay on Monterey until Sonoma comes out to switch to Ventura?
The first OS from Apple I used (and what made me switch to macs for work).
I have been spoilt, starting with the very best.
I remember also Mountain Lion being fairly stable.
After that, I never truly experienced a completely staboe build.
update break update break update break. (I guess apple is expecting different results, and you know what they say about that..)_
This is why macOS should be like a rolling distro, upgrading whenever things are ready, not when the marketing department needs to fulfil a leaflet
I used to live looking forward to the following release to fix the old bugs
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.
Last edited:
Apple is really stepping up their privacy-first approach to everything.
Glad it's here. Hopefully it puts a bit more pressure on them to fix it.
The implications of this issue are extreme.
The fact that this bug was released implies their software practices are a train wreck. The fact that this bug wasn't fixed quickly means they are struggling with it.
I have to take a breath and let that sink in. I'm trusting their software with a lot of stuff. They don't deserve that trust. Any organization that releases a bug like this reveals how inadequate they are in basic software practices. Any organization which can't quickly fix such a bug reveals how little control they have over their own code base.
What we see here of Apple is impossible to unsee. They need to do more than fix the bug. They have to explain themselves; how did they let it happen and why couldn't they fix it quickly. How are they going to change to not let something like this happen again.
The fact that this bug was released implies their software practices are a train wreck. The fact that this bug wasn't fixed quickly means they are struggling with it.
I have to take a breath and let that sink in. I'm trusting their software with a lot of stuff. They don't deserve that trust. Any organization that releases a bug like this reveals how inadequate they are in basic software practices. Any organization which can't quickly fix such a bug reveals how little control they have over their own code base.
What we see here of Apple is impossible to unsee. They need to do more than fix the bug. They have to explain themselves; how did they let it happen and why couldn't they fix it quickly. How are they going to change to not let something like this happen again.
Last edited:
I fully agree this bug should have been caught and fixed in this release. More so if this bug had been reported during the beta testing phase. If it wasn't discovered, I don't know what the beta testers were doing.
I am very sure apple has received the bug report. Whether they read it or not and prioritize it above anything else is the question. It seemed they had a schedule for releasing the update and had reached a point where further bug discovery could only be fixed in the next point update rather than the current one.
But it is strange this bug was introduced during beta testing and persisted. It is strange that Apple has no mechanism to ensure patching bugs without affecting the good working codes. Surely there is a system to mitigate that.
I am very sure apple has received the bug report. Whether they read it or not and prioritize it above anything else is the question. It seemed they had a schedule for releasing the update and had reached a point where further bug discovery could only be fixed in the next point update rather than the current one.
But it is strange this bug was introduced during beta testing and persisted. It is strange that Apple has no mechanism to ensure patching bugs without affecting the good working codes. Surely there is a system to mitigate that.
It's like:
Bozo is a famous surgeon. He generally has good luck with the complex cases. But, there was this time that an infection took hold in one of his patients. Oh well, it happens; it wasn't even that serious. But, then it was discovered that Bozo doesn't always bother washing his hands before operating. Well, the infection was treated and cured, so you might be tempted to overlook it. But, you can never unlearn that the cause of that simple, easily curable infection was Bozo's extreme negligence.
It's not enough that Bozo maintain a reasonable track record with his patients. He has to convince us that he's learned to wash his hands. If not, you just know that infections will keep happening.
We see Apple's incompetence in plain display with this bug. That incompetence will cause minor bugs, major bugs, and everything in between. The first order of business is not to fix the bugs; it's to fix the incompetence.
Bozo is a famous surgeon. He generally has good luck with the complex cases. But, there was this time that an infection took hold in one of his patients. Oh well, it happens; it wasn't even that serious. But, then it was discovered that Bozo doesn't always bother washing his hands before operating. Well, the infection was treated and cured, so you might be tempted to overlook it. But, you can never unlearn that the cause of that simple, easily curable infection was Bozo's extreme negligence.
It's not enough that Bozo maintain a reasonable track record with his patients. He has to convince us that he's learned to wash his hands. If not, you just know that infections will keep happening.
We see Apple's incompetence in plain display with this bug. That incompetence will cause minor bugs, major bugs, and everything in between. The first order of business is not to fix the bugs; it's to fix the incompetence.
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...
iOS 16 was probably the buggiest iOS release ever. It's gotten a little better now that we're about midway through the dot releases.