Bug #5427


Added by R S almost 5 years ago. Updated about 1 year ago.

Status:Blocked Start date:12/06/2017
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:(All models)


I could not install the Mac OS version of CHIRP into:

MacBook Pro macOS Sierra 10.12.6

I followed the instructions below: unzipped, control "click" the app entered the command line.

The result was a new window with "CHIRP" in the top bar but the rest was blank.

PLEASE help.

" Application Security in 10.12+
As of 10.12 (Sierra) the UI for disabling app security was removed. The functionality is still there, but must be enabled from the command line.

To whitelist a single application (like an unzipped chirp-daily.app):
unzip chirp.zip
control click on the unzipped application and select New Terminal at Folder. (Don't see that menu item? Instructions to enable it)
run this command in the newly opened terminal window:
spctl --add $PWD "


Updated by R S almost 5 years ago

Solution found.

Updated by Michael Gearhart almost 5 years ago

I am having the same issue. I have tried the fix to Application Security in 10.12.+. Nothing seems to start and nothing to shut down in Force Quit. Would like to use this product, but it does not seem to work on the Macbook Pro model for some reason. Could there be an application or a driver conflict issue? Thanks.

Updated by Michael Gearhart almost 5 years ago

Issue is that python runtime is not installed. This is not in the basic install instructions

Updated by Bernhard Hailer over 2 years ago

  • Status changed from New to Blocked
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily
  • Platform changed from Windows to MacOS

Keeping open until this has been added to Wiki.

Updated by Martin Cooper about 1 year ago

Per the Download page, the preferred way to install Chirp on Mac is now to use the MacOS Unified Application. This application is a self-contained bundle that includes the required Python version and all other dependencies. You should no longer encounter this type of issue with missing requirements.

Also available in: Atom PDF