top | item 42032444

Apple Removes Ability to Run Unsigned Apps in macOS 15.1

38 points| TheRealDunkirk | 1 year ago |lunduke.locals.com

19 comments

order

486sx33|1 year ago

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.

conartist6|1 year ago

yeah they tossed bluetooth AptX support from the OS (that I used all the time) without telling me and handled it in a similar "Too late now!" kinda way. Guess I was the sucker for trusting them.

kappuchino|1 year ago

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.

snvzz|1 year ago

Is it really a bug, or is it A/B testing I wonder.

Like they're testing the waters, to see how people react.

conartist6|1 year ago

Wow, I guess I'm never upgrading to that OS version or buying more Apple hardware for development when this puppy dies.

Buttons840|1 year ago

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.

crest|1 year ago

This the article claims Apple removed that workaround (needed since macOS 15.0) completely in macOS 15.1.

cjk|1 year ago

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.

nunez|1 year ago

Apple removing the ability to run unsigned software entirely would footgun Mac sales. No way they would do that.

devvvvvvv|1 year ago

Hopefully just a bug. If not, Apple should be ready for more expensive legal battles (at least in the EU).

chrsw|1 year ago

Even if it's not a bug, at least there's still a workaround. For now...

twohaibei|1 year ago

I dont think it's a bug, but i sure hope it will be reversed.

rootusrootus|1 year ago

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.

throwuxiytayq|1 year ago

What kind of a god-forsaken OS has bugs that completely take away your ability to run [unsanctioned] software? Food for thought.

asmnzxklopqw|1 year ago

Is the brew ecosystem impacted by this?

mr90210|1 year ago

I bet their own engineers would be impacted by that.