Fixing error: “app_name” cannot be opened because the developer cannot be verified.

Check where the app is installed

$ which app_name

Lift the quarantine for the app name binary Now you need to tell Mac OS to trust this binary by lifting the quarantine. Do this by the following terminal command

$ xattr -d com.apple.quarantine /usr/local/bin/app_name

Brew

Fix brew update issue - Mac 11.0 or higher

If brew update doesn't work run this command before running brew upgrade

$ brew update-reset

Brew error updating

Error:
  `homebrew-core` is a shallow clone.
  `homebrew-cask` is a shallow clone.

To brew update, first run

$ git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow

$ git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask fetch --unshallow

These commands may take a few minutes to run due to the large size of the repositories. This restriction has been made on GitHub's request because updating shallow clones is an extremely expensive operation due to the tree layout and traffic of Homebrew/homebrew-core and Homebrew/homebrew-cask. We don't do this for you automatically to avoid repeatedly performing an expensive unshallow operation in CI systems (which should instead be fixed to not use shallow clones). Sorry for the inconvenience!

Error: The following directories are not writable by your user:
/usr/local/include
/usr/local/lib
/usr/local/lib/pkgconfig

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

$ sudo chown -R $(whoami) /usr/local/include /usr/local/lib /usr/local/lib/pkgconfig

And make sure that your user has write permission.

$ chmod u+w /usr/local/include /usr/local/lib /usr/local/lib/pkgconfig

Print all ENV variables

printenv

Export a ENV variable

export AWS_SECRET_ACCESS_KEY=blahblah