Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS Sequoia makes it harder to run not notarized or signed apps

9to5mac.com

Post reply on HN
Print view View original

1–10 of 76 posts

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#2

Post by pjkundert »

This is not good.

I've spend literally days attempting to get a Python-based GUI application "signed", using every available packaging option and dozens of different approaches recommended by a multitude of different sources.

Absolute failure -- and no usable error messages indicating what might be wrong. Just basically "no, you can't upload that.".

This does not bode well...

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#3

Post by ryandrake »

Apple seems to like to coerce their users onto their preferred track little by little, release after release, instead of hamfistedly forcing it on day one. Instead, each release is a small drip of inconvenience and nudging.

Long time ago, you could run any executable you wanted. Then, you got a little nag, but whatever. Then (I think) you had to right click and take an extra step to run them, with a scary warning. Then, you got an even scarier warning and had to navigate into Settings to select "Allow applications downloaded from" -> Anywhere. Then, they removed the "Anywhere" option, but you could re-enable it with the command line.

It's also directionally clear: They surely intend to fully boil the frog one day and remove the ability to do this.

Se also: The UX you have to navigate in order to fill your own password into web pages on Safari.

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#4

Post by al_borland »

I hope they will at least prompt the user to let them know what’s going on. I’ve run into this before on macOS, where an app wouldn’t launch, and on a hunch I went into the security settings and saw a section there were it was blocked and I could allow it. There was not even a hint of this in the error message when trying to launch the app. It was a very poor experience.

I’ll also be curious if placing the app in ~/Applications avoids the restriction. This has long been my way to get around some of the restrictions at work. /Applications requires admin rights, ~/Applications does not. Apps still show up in LaunchPad and work as normal (as far as I’ve seen), they are just only available to the user, instead of all users, which is fine for my situation. I used to have to request admin rights every time VS Code wanted to update on my work laptop, but since I put it in my user folder instead, it’s been smooth sailing.

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#5

Post by talldayo »

pjkundert wrote: post #2

This is not good. I've spend literally days attempting to get a Python-based GUI application "signed", using every available packaging option and dozens of different approaches recommended by a multitude of different sources. Absolute failure -- and no usable error messages indicating what might be wrong. Just basically "no, you can't upload that.". This does not bode well...

> This does not bode well...

What, in the past 10 years of MacOS development trends, suggested to you that anything was headed in the remote direction of "boding well"?

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#7

Post by pjkundert »

talldayo wrote: post #5
pjkundert wrote: post #2

This is not good. I've spend literally days attempting to get a Python-based GUI application "signed", using every available packaging option and dozens of different approaches recommended by a multitude of different sources. Absolute failure -- and no usable error messages indicating what might be wrong. Just basically "no, you can't upload that.". This does not bode well...

> This does not bode well... What, in the past 10 years of MacOS development trends, suggested to you that anything was headed in the remote direction of "boding well"?

Admittedly, I've done 99% of my development to target Linux, and just happen to use a Mac for its simpler and less time-consuming day-to-day GUI management.

This is the first time I've tried to develop something to target a macOS installation -- and it was a train-wreck.

Re: macOS Sequoia makes it harder to run not notarized or signed apps

#8

Post by burnte »

pjkundert wrote: post #2

This is not good. I've spend literally days attempting to get a Python-based GUI application "signed", using every available packaging option and dozens of different approaches recommended by a multitude of different sources. Absolute failure -- and no usable error messages indicating what might be wrong. Just basically "no, you can't upload that.". This does not bode well...

Sounds like it's working as Apple has intended.
Post reply on HN