I was starting to create an android application in Eclipse Juno. I filled out all the neccessary requirements but when I'm about to click the finish button, it won't work. I can click it though but it won't open a new android application workspace for me and I'm like stuck on it for hours. Can somebody tell me what to do? Thanks.
The version of your SDK it not compatible with the JDK. All you have to do is to install the last version of JDK by use of the tool manager of eclipse of by searching for JDK on google and then directly installing it.
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
I am attempting to use the android plugin for eclipse (Indigo), and I've gotten it to work once. Unfortunately the machine I am using has a 'deep freeze' program on it, and so I've had to install the SDK several times in order to use it. I have permision from the system administrator to install the SDK permanently, but I cannot seem to get it installed correctly. My problem is as follows:
I follow the instalation instructions found on http://developer.android.com/sdk/installing/index.html, have a few problems making Windows recognize the fact that the JDK is already installed (which I work through), and then complete the installation. I attempt to create a new Android project and in step 1 of the project creation the drop down bar labelled 'Build SDK' is completely blank, and the 'next', 'back', and 'finish' buttons are all dark and unclickable.
I'm not quite sure what I've done differently from installation to installation (of the SDK). Any help or suggestions would be apreciated.
I have recently updated my ADT and it is now ADT_V20. I have also updated my SDK platform tools as well. But I am not able to create new Project through Project wizard from Eclipse.
I have Eclipse Helios latest version. and It was working well with old ADT versions.
In the project wizard I have reached upto Install Dependencies screen, where "Next" and "Finish" buttons are disabled. I have tried to "Install/Upgrade" new version as shown in the wizard and that process is completed successfully . Still I am not getting "Next" or "Finish" buttons enabled.
This same thing happens on the other PCs as well.
Could anybody please help me ?
Thanks
Looks like you can get around this issue by uninstalling the Support library from the SDK manager, then reinstalling at the prompt in the wizard. I had the same problem you did, and this solution worked for me.
Source: http://code.google.com/p/android/issues/detail?id=33859
In the new Android Project Wizard on the second screen where is says "Select whether to create an activity, and if so, what kind of activity"
Simple un-check the Create Activity, A new Blank Activity will be enabled to be created. -
Click Finish.
They might push a fix for the issue you have highlighted soon.
I have come across some more issues related to Ant build.xml not able to find "com.android.ant.NewSetupTask" due to this upgrade to ADT20
After installing ADT version 20, I have this problem creating a 1.6/API 8 project now that the newer (version 20) SDK is installed.
Would one of the experts try creating this even WITHOUT the 'activity' please?
I cannot complete with the blank activity checked (due to the missing API 8, which tries to install the already installed API 9 when asked to update), NOR can I complete with NO activity selected.
In the latter case, i.e., uncheck the create Activity box, the Finish button appears, creates the project partially, but not one that will build (as the older versions would do even with an old API.
Also, there is no actual indication that the "Finish" has worked -- you must look over in the browse pane to see the new project even though the dialog remains.
If any of the above did n't solved your problem please do one thing, try DELETING org.apache.log4j_1.2.17.jar from eclipse/plugin directory !!!!
In MACOSX, with Eclipse Helios IDE, this solution didn't work for me. I solved the problem uninstalling the components by the SDK tools and installing them again by the same SDK manager. I tried to reinstall the components by the same new project dialog, but didn't work for me, my only solution was that, uninstalling and reinstalling from sdk manager.
I hope this solution works for you :)
My solution is that I found out that Android Support Library was not installed on my computer (I didn't even have an Android folder under extras/. I ran the SDK Manager as Administrator, selected this and installed it. Then I tried creating a new project and I got the same error. I clicked Install/Upgrade and the Finish button became enabled. The next time I created a new project, I didn't get this error.
In my case the app had been created, but I didn't see it as it was completely obsqured by the welcome splash screen. When I didn't see it, I tried to create the app again, and it was failing to finish silently. Only when I ventured to close the splash screen did all become clear.
When I create an android project in Eclipse (Helios) and open for example main.xml and click on layout view - program closes. If I start eclipse over again and try click in project view on main.xml it happens again.
In the official installation instructions for Android, they tell you not to use Eclipse 3.6 (Helios). Not that many people notice, three lines above that, they still tell you to use "Eclipse 3.4 and above", plus the link they still have there (http://www.eclipse.org/downloads/) points to the latest Eclipse, which is currently 3.6!
The real link is http://www.eclipse.org/downloads/packages/release/galileo/sr2
I urge you to do things correctly and reinstall Eclipse. You may have other problems if you keep 3.6. For instance, on some (but not all) computers, Eclipse 3.6 (Helios) may hang (or gets really slow) when doing auto-complete (it's looking for a non-existent folder).
Also, you won't be able to find Eclipse 3.5 Classic as the documentation still says, Eclipse Classic Galileo is no longer available on Eclipse.org, instead you should install Eclipse Galileo RCP 32-bit (Galileo doesn't have a good 64-bit version).
Just be sure to do a check for all updates, then install the ADT update site, restart eclipse, close all perspectives, reopen the Java perspective, and go to Windows > Preferences and click on 'android' on the left and make sure it found the old location of your android sdks.
Turned out that I had 2 virtual machine- 1.5 and 1.6, in Java Settings tab of project settings I set the path to the new version and UI view has become operational.
Try to right click on the main.xml document in the project navigator and select open with a different method. Can you get Eclipse to open it any of the other built-in ditors?