Android Studio, the shiny new Integrated Development Environment for Android released this Google I/O has been receiving overwhelmingly positive reviews from developers. The new studio is based on JetBrain’s IntelliJ based developer tools and brings in extra functionalities on top of it for Android SDK such as Gradle-based build support, real time simulator for reflecting changes in code and much more.
While the new Studio is excellent in terms of capabilities, the procedure of migrating workspace from Eclipse to Studio has been giving some issues to several developers, particularly related to the Android SDK.
One such problem that I personally encountered while trying to migrate to Android Studio was its inability to find Android SDK, which was weird since I already had SDK installed on my machine and it was running fine in conjunction with Eclipse.
No Android SDK Found. Please configure an Android SDK.
Solution for Android Studio No SDK Found. Please Configure an Android SDK Problem
Step 1. Update your copy of Android SDK
Navigate to the directory where Android SDK is installed and open SDK Manager.exe.
Next, check whether the SDK is updated to the latest version i.e., revision 22 or not and update it if required.
Here’s a direct HTTP link if you prefer downloading the update from a separate program such as a download manager:
Android SDK Tools r22 update (95 MB)
Note: (For manual update only) For applying this update, move its contents to the SDK directory, replacing all the files and folders if asked.
Restart Android Studio to check whether updating the SDK solves the problem for you or not.
Step 2. Verify the Android SDK location
If the above step didn’t work its magic for you, verify if there’s any android-sdk folder located in the following address:
X :\ Users \ <Username> \ AppData \ Local \ Android
Replace X with the drive letter where Windows is installed and <Username> with your Windows username. Also, AppData is a hidden folder and so, you’ll have to first enable the option to show hidden folders in the Windows explorer.
Chances are that Android Studio might be using this directory of Android SDK instead of where you had actually installed the SDK from its setup. If this turns out true for you, move all the files from the original SDK location to this address.
This step, combined with the first one solved this issue for me. Feel free to drop a comment if you have any questions.
If switching your workspace to the IntelliJ based Android Studio is proving too cumbersome for you, you can continue to use Eclipse for your development needs.