Using 3.6.2. When I choose to create a new Android Project, I enter a name, 'FirstProject' but the Finish button remains hollow and I cannot get past creating the project.
I did a little Google research and found a common cause of this is that the support folder that exists in the SDK's extras folder needs to be duplicated and the duplicate named to compatibility. I've done this now, and restarted Eclipse, but this still hasn't fixed the issue.
I also read that Juno causes this problem, but I'm not using Juno.
Has anyone experienced this problem before? Very eager to start an Android App!!
EDIT: A screen of the error:
You need to choose a Build SDK. If there is nothing in that drop-down, please visit the SDK Manager (Window > Android SDK Manager) and download one or more SDK platforms and associated emulators.
Make sure you add the SDK in Eclipse otherwise you will download them all and scratch your head on why they are not working.If you launch SDK manager form SDK folder and not from Eclipse it does not seem to register in Eclipse that you have downloaded these files. Took me several hours for something that should have taken only one or so.
Related
I have downloaded ADT Plugin for Eclipse. I don't see Android anywhere either when creating a new project, Preferences or "Customize perspective"
I have searched for the answer but I couldn't find it. The only thing that I didn't try is opening "command group availability" tab mentioned in forum not showing Android And AVD manager in eclipse because I can't see it at my setup.
I'm using Eclipse Neon.2 with JDK jdk1.8.0_121. I didn't add a PATH variable in my system. Not sure if I have to or not.
Android ADT doesn't seem to work for me in Neon too (same errors and long time search on startup without results)
There is a new Eclipse Android dedicated IDE now at https://eclipse.org/downloads/packages/eclipse-android-developers-includes-incubating-components/neon2 Must be installed in a separate folder with separate workspace (and renamed if needed) and all existing Android projects can be moved there. Afterwards i uninstalled ADT from the original Eclipse folder.
There is Installation Instructions for Google Plugin for Eclipse 4.6 (Neon)
https://developers.google.com/eclipse/docs/install-eclipse-4.6
It appears that either Eclipse Neon.2 stopped supporting ADT or that it has issues with it. I went back to Eclipse Neon.1 and I can find Android references all over, so I think the issue is something to do with Eclipse Neon.2.
Thanks to all of you who tried to help.
UPDATE:
It appears that for Neon.2 there is a separate package for Android that you can find here:
http://www.eclipse.org/downloads/packages/eclipse-android-developers-includes-incubating-components/neon2
I downloaded the Android ADT Bundle for Windows and downloaded all the necessary tools to go along with it. Then I started a new project but there is an error in the mainactivity.java. Now I have searched for the answers here and other sites, none has helped me so far. I know the missing file is the R.java. I read here somewhere that it was the Android Build Tools. I noticed something, when I opened the SDK Manager outside of Eclipse, the Build Tools needed are installed. But when I open the SDK Manager inside Eclipse, it's not installed. Is that supposed to be like that? So I need to update my SDK Manager inside Eclipse? And another thing, downloading from the SDK Manager is so damn slow...any tips to make it normal speed? Thanks guys!
R.java is created with your app. Its not anything to download. Do a Clean Project if you are having errors.
As for the internet speed, it depends on your ISP.
I am an experienced programmer but new to Android, hence using Eclipse for the first time.
Unfortunately I cannot get my first project off the ground. I get as far trying to create the project when the following sequence happens.
A screen arrives titled 'Install Dependencies' telling me that the required version is 8 and the installed version is 'Not installed'
I click on the Install/Upgrade button and something must happen because Android SDK Manager pops up and I get a whole series of 'Fetching:' messages.
The next screen asks me to Choose Package to Install and the only option is Android Support Library, revision 10. This doesn't bother me as I presume 10 is better than 8 so I hit the Install button.
This is where it all goes wrong as I get a red message saying:-
File not found:C:\Program Files (X86)\Android\android-sdk\temp\support_r10.zip (Acces is denied).
Sure enough, when I check this folder, it is empty.
Now, something must have happened as as SDK Manager did a whole lot of fetching and must have put these files somewhere.
I am quite happy to find them and put them in the correct folder but the question is
What is the name of the files that I am looking for?
Run SDK Manager as administrator and then install Android Support Library from Extras
Download the sdk manager seperately and install files from there. put it in a place which is accessible to you and then point your eclipse android directory to it. tools>options>android sdk
Run eclipse as Administrator. This is the solution.
Try running your application (Eclipse) in Admin Mode.
Right click on the Eclipse app, and choose "Run as Administrator"
This will fix your problem.
properties >java build path >click library tab > add jars > add jars from the support library.
I am new to the android development and when i create a new project using eclipse juno on mac OSx i got an error at runtime Failed to instantiate com.android.menubar.internal.MenuBarEnhancerCocoa
And yes on the layout file it also says- The project target(Android 4.1) is not properly loaded.
Anyone please help me how to get out of this. Thanks in advance..
And yes everything was setup properly SDK and all, because this whole setup is running properly on one of the other system.
I had the same problem but managed to resolve it. com.android.menubar.internal.MenuBarEnhancerCocoa - was not in the SDK that was linked to Eclipse install (I have multiple for various reasons - e.g. AppEngine not supported in latest Eclipse). There were a number of steps I had to do to resolve this (so any one of them may be the actual fix or a combination may resolve the problem).
Here's a checklist :
If you have installed Eclipse - click the Android SDK manager icon. Ensure it is pointing to the latest Android SDK (R20 as of writing)
As it's a new Eclipse+SDK - add the build targets by selecting from the list of targets that appear in the SDK manager. Also add Android support tools
Restart Eclipse. When asked about he workspace - create a new one. I thought some of my problems would be linked to old projects.
The problems should have gone away. One final thing is, once you create a project - check your certificates have not expired. There's another thread on updating the debug certificate (Delete your keystore located in ~/.android/debug.keystore then restart Eclipse.)
Create a new AVD target.
Hope those things help.
It appears to me the com.android.menubar.internal.MenuBarEnhancerCocoa is only there to make the android app feel nicer if it's run directly. Then preferences and about will be in the application menu. If you run the android sdk manager from eclipse, then eclipse will take over that part of the application menu.
Although it doesn't sort out the issue it may be useful anyway. There's the web page with the sources MenuBarEnhancer where there's the call to instantiate the com.android.menubar.internal.MenuBarEnhancerCocoa class.
eclipse is working fine with importing a project which already exist. But i am facing problem while am creating a new project in the android.
And then am trying to change the path in the properties of the project which i have created then it is showing some kind of error and screen shot of it is
Can any one help me in this.
Assuming your d: drive is an actual hard drive you have the android-sdk in, and not some DVD/CD drive you tried installing the android-sdk from.
You should click on your new android project folder, right-click and click on "close unrelated projects", then the right files will get generated correctly (re-initiate a manual rebuild if you have to).
The problem was that Eclipse was trying to rebuild all the projects you had in your workspace, a number of which already contained errors in them. Not only those other projects were clogging up your error log, but when an error is detected by the packager/builder, the building process gets stopped entirely.
Now just in case this wasn't your only problem, do Help > Check updates
After that, click on the menu Window > AVD Manager and something
and make sure that you have the latest SDKs and AVD updates already installed.
Also be aware that Pulsar is not the recommended version of Eclipse for doing Android development, although this probably wasn't what was causing your problem.