NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
In macOS Sierra
, the security around apps from unidentified developers has really been tightened. In previous releases of the OS
you were given an option to open the app if it came from an unidentified developer but it seems that Sierra
just gives you the 'OK'
option and will not launch the app. There is a way around it however so read on for how to do it.
This ist he kind of message that you'd typically be presented with when launching an app from an unidentified developer:
"ExifTool-10.37.pkg" can't be opened because it is from an unidentified developer. Your security preferences allow installation of only apps from the Apps Store and identified developers.
However when looking at the Security & Privacy
settings, there is no option for 'unidentified developers'
any more! What you do see however is a button 'Open Anyway'
for the specific app you've just tried to launch.
So to open the app you want, you actually have to try and open it first, then go to the Security & Privacy
settings and click the 'Open Anyway'
button and then open the app again.
After opening the app for a second time, you are then warned that it is from an unidentified developer again, but this time you are given the option to open it.
Clicking 'Open' will now finally launch the app.
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...