

The only trick that worked for me so far is to launch the Android Studio app via terminal. Re-installing manually and via the Toolbox app even didn't work. Also tried the Invalidate Caches & Restart option. I tried clearing caches in the ~/Library/ directories. I could check this by comparing the Environment variables sheet in Preferences between IntelliJ and Android Studio.


I had another IntelliJ version installed too but it didn't have this issue. My iTerm2 could still recognize this and could echo JAVA_HOME correctly. The JAVA_HOME was already exported in the. My Android Studio was installed manually before. And after restarting it, I ran into this issue and the issue #188. Somehow while Android Studio was still open, my MacBook crashed. Then gradle-doctor will be run during project sync in AS and it likely relies on JAVA_HOME as "known" by the IDE. Then today a colleague installed AS stable on ARCH (with JAVA_HOME already defined correctly), and experienced the same.įrom what I can tell, it looks like AS has a wrong or no value for JAVA_HOME (it cannot "retrieve" it from the system on start for some reason). I've experienced it on Ubuntu when we enabled gradle-doctor and I am working around it by exporting JAVA_HOME at the top of the AS studio.sh launch script. | echo "export JAVA_HOME=$(/usr/libexec/java_home)" > ~/.bash_profile |Īnd yes, tried restarting AS, restarting my machine, and this actually happens on a fresh install of AS and both in stable, beta and canary. | Please set JAVA_HOME so that switching between Android Studio and the terminal does not trigger a fu | Before, when clicking the back button, the application returned to the previous page, after adding the shouldOverrideUrlLoading the application is closing and not showing the previous page of the webview.> = Gradle Doctor Prescriptions = OnBackPressed() was working perfectly before adding shouldOverrideUrlLoading.
