Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>OK, I figured out how fix this nasty bug.</p> <h2>Before you start</h2> <p>Go to your Android Studio installation folder and locate the bin folder. Inside the bin folder, you will find <strong>studio.bat</strong>. Execute the file, and it'll show the error. If it is about the Java path then follow the tip 1.</p> <h2>Tip 1</h2> <p>When you set the path <code>JAVA_HOME</code>, etc., make sure not to include <code>bin</code> at the end of the path. This solved the issue for me.</p> <p><code>JAVA_HOME</code> => <code>C:\Program Files\Java\jdk1.7.0_21</code></p> <p><code>path</code> => <code>C:\Program Files\Java\jdk1.7.0_21\bin</code></p> <p>It works fine with JDK 1.7 (I tried with 32 bit).</p> <p>If you do so, you can see the initial screen as below.</p> <p><img src="https://i.stack.imgur.com/pAuaV.png" alt="Enter image description here"></p> <h2>Tip 2</h2> <p>Are you getting the below error message?</p> <blockquote> <p>Your Android SDK is out of date or is missing templates. Please ensure you are using SDK version 22 or later.</p> </blockquote> <p>This error probably occurs, because you have reference to your older SDK (that you downloaded with <a href="http://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="nofollow noreferrer">Eclipse</a>) in your path variable. Go to Environment variables and remove any reference to the old SDK folder and point it to new SDK folder that is found inside the Android Studio installation folder.</p> <p>Save and restart Studio, things should work as expected now. </p> <h2>Tip 3</h2> <p>If you hate messing around with the path variable as given above by removing old references, simply follow the following steps to refer to new SDK path that comes with Studio.</p> <p><code>*Project Defaults* -&gt; *Project Structure* -&gt; Click "New" -&gt; Select "Android SDK" -&gt; Select the SDK</code> folder inside the studio installation.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload