title: Broken AVD system path - But ANDROID_SDK_ROOT is defined and correct?
body: <p>I'm facing a really bizarre issue. I have a continuous integration service setup across a few identical machines locally. I just recently went to add a new machine to the cluster and I'm all of the sudden getting the <code>"PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [/usr/local/share/android-sdk]!</code> error when this new machine tries to start an Android emulator. </p>
  
  <p>The same install script to get a new instance online was used on all previous instances which are running fine.</p>
  
  <p>The script installs the following dependencies (amongst others that are not related) via brew in order to run an Android emulator locally:</p>
  
  <pre><code>brew cask install java
  brew cask install android-sdk
  brew cask install android-platform-tools
  brew cask install intel-haxm
  </code></pre>
  
  <p>Everything required is definitely in the <code>/usr/local/share/android-sdk</code> directory. The system-images, tools, platform-tools directories, etc.</p>
  
  <p>I've done my own probing to try and figure this out. Additionally, I've checked the versions of the dependencies installed on this machine, and the version running on machines that are having no issues and they're the exact same...</p>
  
  <p>I'm out of ideas on where to look.. Any suggestions would be greatly appreciated.</p>
  
  <p>The environment variables are the same between both machines as well.</p>
  
  <p>Note: These machines DO NOT install Android Studio.</p>