by 486sx33 on 11/3/24, 12:04 PM
Funny, there were no notes or warnings about this when I clicked “update now” and of course, OS updates can’t be rolled back…
Not sure what Apple is doing here but it sounds rather evil.
by kappuchino on 11/3/24, 12:54 PM
The Author didn't check if they have a unique problem ... it it seems they have an individual issue. Which is still shit, but not the kind of suggested by the alarmist headline.
I checked my version, it its 15.1. on a M2 Macbook Air. Its fine.
Same for at least 3 other people I asked and which checked.
by conartist6 on 11/3/24, 12:19 PM
Wow, I guess I'm never upgrading to that OS version or buying more Apple hardware for development when this puppy dies.
by Buttons840 on 11/3/24, 12:18 PM
I haven't found much information about this online. One YouTube comment claimed Apple has only removed the ability to launch unsigned apps via right-click, but you can still open them deep in the setting menus.
by cjk on 11/3/24, 1:01 PM
This claim does not appear to hold water. Works fine for me on both an M1 Ultra Mac Studio and M2 Max MacBook Pro running macOS 15.1.
Seems like it’s just a bug that the author is experiencing.
by nunez on 11/3/24, 2:59 PM
Apple removing the ability to run unsigned software entirely would footgun Mac sales. No way they would do that.
by devvvvvvv on 11/3/24, 11:33 AM
Hopefully just a bug. If not, Apple should be ready for more expensive legal battles (at least in the EU).
by rootusrootus on 11/3/24, 12:34 PM
Hasn’t affected me. And I use a bunch of homebrew installed software.
The error message shown on that blog looks more like a bug than a policy message.
by asmnzxklopqw on 11/3/24, 11:47 AM
Is the brew ecosystem impacted by this?