Mac OS Catalina & Blockdaemon


Mac OS Catalina & Blockdaemon

With the release of Mac OS Catalina, we’re reviewing all of our help content in-app and on the Help Center to ensure that it is up to date and leads to success using Catalina and older versions of Mac Os. 

In general, since nodes are operated in the cloud on your behalf, there will be challenges if you wish to upgrade to Catalina and use Blockdaemon.

We have performed several upgrades and seen very few issues, but wanted to highlight some errors you may encounter on your system if you’ve been using tools to interact with Blockdaemon previously. 

Brew-specific issues

Our Hyperledger Fabric documentation leads users through installing packages via Brew. It’s possible that your installation of Brew may need an update after an upgrade to Catalina. 

If you see error messages such as the following:

Warning: You are using macOS 10.15.

We do not provide support for this pre-release version.

You will encounter build failures with some formulae.

Error: The following directories are not writable by your user:

Note: Please create pull-requests instead of asking for help on Homebrew's GitHub, Discourse, Twitter or IRC. You are responsible for resolving any issues you experience, as you are running this pre-release version.


You should change the ownership of these directories to your user.

  sudo chown -R $(whoami) /usr/local/bin

And make sure that your user has write permission.

  chmod u+w /usr/local/bin

You may benefit from ensuring your installation of Brew is up to date. 

  1. Run the command brew doctor and take note of what it recommends. We have seen errors mentioning git not being in a user’s path, xcode command line tools missing, etc. 
  2. To install xcode command line tools run the command
    xcode-select -install 
    You will be prompted in the Mac OS interface to confirm download, and it will download and install like a normal system update. Close and relaunch your terminal window. 
  3. If you are unable to resolve /usr/local/bin permissions issues, you can solve the issue as well by uninstalling and reinstalling brew itself.
    To uninstall:
    ruby -e "$(curl -fsSL >"
    /usr/bin/ruby -e "$(curl -fsSL"
  4. After installation, run brew cleanup and brew doctor to ensure all issues have been addressed.

In extreme cases (which appear to be limited to day-one upgrades of Xcode), you may benefit from completely deleting and reinstalling Xcode from your system. This is not a common case but one we did encounter on one machine. 

Verify Before You Upgrade

For any system which you cannot afford incompatibility or downtime on, we echo conventional wisdom: you may want to wait to upgrade to ensure all tooling and applications you rely on are compatible with Catalina. While your nodes will continue operating without interruption, we don’t want you to deal with any workflow-blocking issues.

We are re-evaluating every command we instruct users to run, and we will ensure that any issues arising from bash commands not translating to zsh are fixed, documented or explained clearly. 

If you have any issues with in-app prompts or Help Center documentation yielding unexpected results, don’t hesitate to reach out to and we will help resolve your issue as quickly as possible. 

0 out of 0 found this helpful



Please sign in to leave a comment.