Not sure how that's proof of anything. Likely bigger customers had even bigger problems and Apple had to take care of that first.Meaning that I’ve had serious problems in the past and the vast majority of bugs have received an apathetic response.
Not sure how that's proof of anything. Likely bigger customers had even bigger problems and Apple had to take care of that first.Meaning that I’ve had serious problems in the past and the vast majority of bugs have received an apathetic response.
I’ve been an Apple customer for over two decades and have seen, first hand, a major change in the way Apple creates and supports products, and not for the better.Not sure how that's proof of anything. Likely bigger customers had even bigger problems and Apple had to take care of that first.
Why would I want to enter my password when the prompt is unclear?
anecdotal.I’ve been an Apple for over two decades and have seen, first hand, a major change in the way Apple creates and supports products, and not for the better.
This is due to a shift away from “insanely great products” to a move towards “insanely high profits”. This has been a documented change and is well written about in Tripp Mickle’s book “After Steve”.
After Steve: How Apple Became a... https://www.amazon.com/dp/0063009811?ref=ppx_pop_mob_ap_share
Because MacRumours is filled with nerds that must be on every latest software because as Tim Cook said "latest is greatest" and they don't understand somebody out there use Mac for real work instead of sending cat pictures on Messenger.I have no idea why your comment recieved a downvote. Tried to look at it objectively but can't see anything terrible in what you said.
Response was measured, no hyperbole and even a suggestion for remedy.
I will say though, I think that the chances of Apple allowing a downgrade are pretty much zero. What they'll do instead is create another build of the same point release. Which doesn't fix the problem of course.
There should an option in Xcode to add manually different toolchain. I used this once on El Capitan but it's tricky and probably nobody in the world used this with success. Developers are rich men and instead working as long as they can on their machines they buy new one because why not.oh this is bad and will screw over a lot of developers. Big time as Apple has removed rosetta support in xcode 15 so they are trapped on Xcode 14.3. Next catch is Xcode 14 does not run on the latest OS.
This just is going to make worse. I have to keep xcode 14 running for a little while for debug purposes or I need to build an earlier version of the code to debug. I personally plan on upgrade my work machine next month but it is common for me to want to hold onto a working copy of the previous Xcode for almost a year so I can drop down into it for an older build to check something.
I get that but I'd actually really like to understand the position.Because MacRumours is filled with nerds that must be on every latest software because as Tim Cook said "latest is greatest" and they don't understand somebody out there use Mac for real work instead of sending cat pictures on Messenger.
Happened here as well, auto-update from Ventura on a 2019 MBP. Explicitly don't have auto-updates enabled due to music software and hardware compatibility, then Apple decided to upgrade for me. Fortunately it's mid-lifecycle for Sonoma. Had this happened when Sonoma was just released, many workflows would have been completely broken...
Over the past few weeks, some Mac users have complained that their computer automatically upgraded itself from macOS Ventura to the latest macOS Sonoma release, even with the automatic updates setting turned off.
![]()
There are widespread complaints about this issue across the Apple Support Community, MacRumors Forums, Reddit, X, and other websites.
In most cases, it appears that affected users received a desktop notification alerting them that macOS Sonoma was an available software update. However, despite dismissing the notification and having automatic updates turned off, affected users said their Mac proceeded to install macOS Sonoma regardless. Apple began showing the notification to users on January 10, according to MacRumors contributor Aaron Perris.
The underlying cause of the issue is unclear, and an Apple spokesperson did not immediately respond to a request for comment.
It is possible to downgrade a Mac to an older macOS version by using a bootable installer to erase and install the older version and then restoring your data from a Time Machine backup. Always make sure to back up your data before downgrading a Mac.
To review your Mac's update settings, open the System Settings app, click General → Software Update, and click the info symbol next to Automatic Updates.
We will update this report if new information becomes available.
Article Link: Some Macs Auto-Updating to macOS Sonoma Without User Permission
Dunno about you but I do/have a LOT more on my computer than I do on my phone. A broken Mac has more implications for me.Interestingly, there has been a lot more outrage about this (a reversible software update, as annoying as this is), than there was with the A9 on iOS 9 activation bug.
iOS disallows downgrades. All A9 devices on iOS 9 were deactivated for some inexplicable reason and forced to update. This happened to me twice.
So folks... it could always be worse. It could be irreversible, and at least this isn’t.
But you can always revert on Mac. It’s irreversible and unfixable on iOS.Dunno about you but I do/have a LOT more on my computer than I do on my phone. A broken Mac has more implications for me.
Yeah I know, I'm saying that's the reason for the outrage. Although you can revert, I think, has the potential for so much more damage?But you can always revert on Mac. It’s irreversible and unfixable on iOS.
There’s no comparison imo. iOS devices are consistently obliterated. Macs? They have a lot more adequate solutions.Yeah I know, I'm saying that's the reason for the outrage. Although you can revert, I think, has the potential for so much more damage?
Well cool. Maybe we look at things differently.There’s no comparison imo. iOS devices are consistently obliterated. Macs? They have a lot more adequate solutions.
Once an iOS device is updated and obliterated, there’s nothing the user can do.