Closed technicalpickles closed 7 months ago
@technicalpickles this is part of security changes made in macOS 10.15.0. Apple now requires binaries to be signed via their developer program, or it will show a message like this & prevent their being opened.
There is a workaround, however!
After seeing that message:
Alternatively, you can:
alfred-weather
executableThe process has no been manually opened and macOS says "it's OK to open in future". You can quit Terminal and everything should be fine.
I always find it much faster to do rather than via System Preferences because sometimes you need to open the app/process again, as well as input your password to unlock System Preferences. It might be worth adding a note/tutorial on how to do this for future users, or even link to this issue.
@noahmaranesi, does that work on macOS 10.15 Catalina? My experience has been that the simpler workflow you’re referring to had been removed. But maybe it’s a bit harder to trigger than it used to be is all?
@jeffbyrnes, I believe so. I know it works on at least macOS Catalina!
Current releases are notarized, so this shouldn't be an issue.
I updated to the most recent release, and I'm seeing this:
I'm on macOS 10.15.6