I have just downloaded AS 4.1.1 and created a new project with "Empty Activity", left the default name and Minimum SDK with defaults.
I get the error in the subject. this is the view of the project:
I made absolutely no change. For the fun of it, I tried "Make project". Nothing happens, no output window to show the build progress/errors, like you would see in most IDEs.
Thanks for your help,
Michel
SOLVED. At first, I upgraded from 3 to 4.1.1. Then I uninstalled AS 4.1.1 and downloaded a fresh install. Still the problem persisted.
I uninstalled again, but this time, I searched for anything Android-related stuff and deleted it, including the SDK under %APP_DATA%\Local\Android\Sdk.
When I re-installed, it prompted me for SDK installation. Selected the SDK and finished installation.
I re-created the application and the error is now gone.
Frankly, I pity the newbie to which this could happen.
I am using Android Studio 3.1 on Ubuntu 18.04 LTS. I'm currently working on a project with target API 28. I've downloaded the SDK with API level 28 during installation but sometimes when I try to run my project on my device, a popup dialogue prompts me to select the SDK. This does not happen every time but happens sometimes even if I've run the project before and made no change to the SDK path. I don't know what triggers this. I've seen similar questions on StackOverflow, but none of the solutions work for me. Here's what I have done so far:
Synced my project
Invalidated cache and restart
closed my project and opened it again
Uninstalled my SDK and downloaded it again
Switched back to an older version of SDK and then back again
But none of this works and the only workaround I found was to open another project that I downloaded from Github (with API 26), build it and then go back to my current project. This solves it temporarily. A few of my friends are working on the same project on different machines (Windows, Mac) and they have this problem, too.
Is this a bug with AS or is there a permanent solution?
File->Settings->Android SDk.
If already was there in your system set the path to that otherwise download the SDK from SDK tools by selecting specific name.
I've found this workaround. It is not perfect, but it works. Hope this this will be helpful for someone else.
Move your project folder to another location and then open it. It resolves the problem.
It shows that I've already installed the Android SDK but I can't find it.:<
Tried in terminal to see what's in the folder but find nothing, this location is empty. Why the app tell me that I've installed it? How can I solve this problem? Thank you!!
I would say that you reinstall Android Studio after checking the SDK Manager at first. The SDK Path may also be corrupted, so check that.
For me it was two issues, proxy settings although tested okay was not connecting to display the list of available SDKs. Also launching Android Studio using "Run as administrator" was also required.
I had exactly the same issue and I came across this post but then before implementing the suggested solutions, I decided to first restart my AndroidStudio, on restart it gave me the option to download SDK and after that, it worked perfectly well.
I have fixed it by downloading the Android SDK from IntelliJ rather than Android Studio.
Then restart Android Studio, It detects the installed version.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
Been away from eclipse and Android for three months, came back to get back into it.
Tried to install two new updates to the SDK (v16 of one thing, v20 of another), which of course failed because I forgot to run eclipse as Administrator, so I got the 'folder failed to be moved' error.
Fine, do it again, seems to finish. Reminds at the end to check eclipse/help/'check for updates', so I did, and let it run while I had dinner.
Now, I'm ready to jump back in.
When I open eclipse, I get the pop-up "This Android SDK requires Android Development Toolkit version 20.0 or above. Current version is 16.0.1.201112150204-238534. Please update ADT to the latest version."
Clicking eclipse / window / Android SDK Manager (where I originally found and authorized these updates), I now get "Location of the Android SDK has not been setup in preferences"
I get the same error as in #2 when I click on AVD Manager on the same menu.
In reviewing some answers here, I got to the "reinstall eclipse" suggestion and decided to write this up and see if a more rational explanation / solution might be forthcoming.
Thanks
Update ADT to a newer version and setup SDK location again. This should be solve your problem.(I'm sorry my answer is most likely a comment, but unfortunately I can't make comments still)
As I feared, I'd read the error msg wrong. Since the SDK manager was telling me the 'Tools' were at 22.0.xxx, I was reading this as the 'Tools' in ADT 'Android Development Tools.' It's not. Went back to the SDK web page from the SDK Read Me.txt, and from that page to the ADT Plugin page, which then led to the 'Installing the eclipse plugin'. Only difference in following those steps was that I didn't have to 'Add' ("Error: duplicate location") because the location to get the plugin was already in the dropdown for 'Work with:'.
COMMENT: Why does this have to be a separate update? Hasn't anyone looked at the SDK Manager's 'Update SDK' process, disconnected from the eclipse ADT plugin update, and thought 'Jeez, won't that create incompatabilities/confusion/difficulties among developers and prospective developers?' I'm not that level of developer in this environment (yet) but c'mon, gang, no one knows how to link the SDK update to a follow-on script to start the ADT eclipse plugin update dialog?