Skip to main content

​
Fix the developer verification error in macOS

By default, macOS will not run an application or tool downloaded from the Internet unless it is signed by an identified developer and notarized by Apple. The macOS builds of ClickHouse are signed with the Developer ID of ClickHouse Inc. and notarized by Apple, starting with the 26.7.4 release (and in every 26.8 and later release). They are published on the GitHub releases page as clickhouse-macos.zip (Intel) and clickhouse-macos-aarch64.zip (Apple silicon), and the Homebrew cask installs them. If you use one of these, macOS runs clickhouse without any warning, and you don’t need anything from this article. You may still see the error if you run an unsigned binary that macOS has quarantined, for example:
  • an older ClickHouse release installed with Homebrew - run brew upgrade --cask clickhouse to get the signed one;
  • the self-extracting clickhouse-macos or clickhouse-macos-aarch64 binary from the GitHub releases page, downloaded with a web browser - download the .zip file of the same release instead;
  • a release older than 26.7.4, downloaded with a web browser.
The binary installed with curl https://clickhouse.com/ | sh is not signed, but curl does not quarantine the files it downloads, so macOS runs it without this error. When attempting to run a quarantined clickhouse binary, you may see this error: If you can’t switch to a signed build, remove the binary from the quarantine, either in System Settings or in the terminal.

​
System Settings process

  1. Try to run the clickhouse binary once, so that macOS shows the error above and records the blocked binary.
  2. Open System Settings.
  3. Navigate to Privacy & Security:
  4. Scroll down to the Security section to find a message saying that “clickhouse-macos-aarch64” was blocked from use because it is not from an identified developer.
  5. Click Allow Anyway (Open Anyway in recent macOS versions).
  6. Enter your macOS user password.
You should now be able to run clickhouse commands in your terminal. macOS may ask you to confirm once more on the next run.

​
Terminal process

If the button in System Settings doesn’t fix the issue, or you prefer the command line, remove the quarantine attribute from the binary with xattr. If clickhouse is in your PATH, find out where it is:
This should output something like:
Remove clickhouse from the quarantine by running xattr -d com.apple.quarantine followed by the path from the previous command:
You should now be able to run the clickhouse executable:
This should output something like: