Java versions. Oh joy.
I’ve been toying with the idea of working through a couple of Android developer tutorials since I grabbed the Moto 360 and started having a lot of “Wouldn’t it be cool if…” wearable moments. Google’s new Android studio is just out of beta, and is intended as a replacement for the aging Eclipse + Android plugin combo everyone’s been using so far. We’ll be seeing an increasing number of tutorials switching to Android Studio in the coming months since support for the Eclipse plugin was just dropped, so this is definitely the best way to start with Android.
Unfortunately, getting Android Studio up and running on OSX Yosemite (10.10.1) required a signicant amount of pain + weird Java version troubleshooting. This is what worked for me.
Get Android Studio
Start with Studio itself, which you can download from the Android developer site.
This installs, but fails to launch with an error because it can’t find Java. This is not surprising.
Get Java, Round 1
Predictably, I tried several different versions of Java. Android Studio docs claim you need 7, and links you to Oracle’s download site, which helpfully tells you that 7’s dying as of March ‘15, and suggests you download 8. Short version after a ton of trial-and-error: download 8. I got 8u25.
This gives me an oddly broken studio install. If I click on the app icon or try to launch it in Quicksilver, it gives me the same error about not finding Java. But opening the app from the command line works fine.
1 Daves-Mac-mini:vm dave$ open /Applications/Android\ Studio.app
Get Java, Round 2
I spent a lot of time trying to figure this out. Changing perms didn’t work, building an Automator script to run the working command didn’t work, attempting to grab the executable inside the app package didn’t work. I suspect this is a permissions / ownership problem.
The fix: go get this OSX Java update from Apple.
This got me a working Android Studio installation that launches as expected from terminal, dock, Apps folder, or Quicksilver.