Cannot install maestro with latest Xcode 14 (homebrew)

[ricardopereira]

Steps to reproduce the behavior:

• Go to the command line
• Run

brew tap mobile-dev-inc/tap
brew install maestro

See error saying maestro cannot be installed because Xcode 13.4 should be installed.

Logs:

➜  ~ brew install maestro
==> Downloading https://ghcr.io/v2/homebrew/core/openjdk/11/manifests/11.0.16.1
Already downloaded: /Users/rp/Library/Caches/Homebrew/downloads/13aaeccdeb47cb9c595339e778c909cdfa349df03dfc046afb6c4303d131b620--openjdk@11-11.0.16.1.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/openjdk/11/blobs/sha256:9c4b44
Already downloaded: /Users/rp/Library/Caches/Homebrew/downloads/2315549e4a0434af3b7c6b6cd91295f4806ed16142e2250aee2c7bc0c415b6fb--openjdk@11--11.0.16.1.arm64_monterey.bottle.tar.gz
==> Downloading https://github.com/mobile-dev-inc/maestro/releases/download/cli
Already downloaded: /Users/rp/Library/Caches/Homebrew/downloads/cfca50391af9f03daec8461c679bf0e906548782a51c5a0db9d4ca04f1abe0fd--maestro-1.6.0.zip
==> Installing maestro from mobile-dev-inc/tap
Error: Your Command Line Tools are too outdated.
Update them from Software Update in System Preferences or run:
  softwareupdate --all --install --force

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  https://developer.apple.com/download/all/.
You should download the Command Line Tools for Xcode 13.4.

➜  ~ xcodebuild -version
Xcode 14.0
Build version 14A309
➜  ~ xcode-select -p
/Applications/Xcode_14.app/Contents/Developer

[irangareddy]

Hi @ricardopereira, just tried the steps you have mentioned. With Xcode 14.0.1 maestro downloaded successfully with homebrew.

I have not encountered any issue. Please try updating the Xcode to the latest and download maestro.

[ricardopereira]

Thanks @irangareddy. It's working for me now. I reinstalled the Xcode command line tools.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. Thank you for helping keep us our issue tracker clean!