Eclipse wont recognize Android support library revision 9 - android

I recently downloaded all the latest updates for my eclipse/Android plugins (before the upgrades everything worked fine). I got everything to work except when i try to create a new project I get a message that I need Android support library revision 8. I click Install/Upgrade and It proceeds to download and install the library. When it finishes the tiny download/install window disappears but the window which informs me that i need Android support library revision 8 remains open and i cant click finish to create new project. I tried closing the window and eclipse and trying it again but it always leads me to the window which states I need the Android support library revision 8. I didnt move eclipse to any other location and I am wondering what is wrong.
I had a problem before with an ! in my eclipse path and eclipse wouldnt work because of exit error 13. I posted a question about it before. My answer explains what has happened and the easy fix.
I am wondering what is wrong now. Do i need to manually link the support library?
Im really frustrated because its taking me forever to set this up.
Update:
I tried restarting eclipse and reinstalling the library multiple times.
I upgraded the android sdk tools and sdk platform-tools before i installed the support libraries.

Like these similar issue i'd for 2 days ago. Whenever, i'm trying to create a new project its showing me like below
For, this i've downloaded that support library using Install/Upgrade and in my path E:/Android/Android-Sdk/extras/android/compaitability I've changed the name of compaitability as support and after just restarted my Eclipse. Its working fine.
Hope these helps you.

Try updating android sdk tools and sdk platform-tools and restart eclipse? ADT has dependencies on these.

Related

Android Studio select SDK error on trying to run project

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.

Eclipse android not creating activity

I've just tried to get into Android development, but somehow I can't get my project working properly. I followed the "Getting Started" guide (http://developer.android.com/training/basics/firstapp/creating-project.html), but I'm stuck on building my project.
Everything is going fine but the creation of my MainActivity. I've left all the settings regarding the activity to default. Somehow when I create my project, there's no activity definition in the AndroidManifest.xml.
I've two potential solutions, but none of them seem to work. The mainly suggested workaround is to update the ADT Plugins through the correct repository (Eclipse android project not creating blank activity). However in my situation the updater states that I've already got these packages installed.
The other possible solution was to remove the support library from the SDK manager. After that, trying to create a new project in Eclipse should prompt me to install this package. Somehow I don't seem to get this prompt. (https://stackoverflow.com/a/11260656/3786210).
Are there any other possible solutions I could try out to get my project correctly built? Thanks in advance!
Additional information:
Windows 8 (64 bit)
ADT packages version: 23.0.0.1245622
Target SDK and Compile With: Android 4.4 (KitKat)
You should just yse IDEA instead of Eclipse
http://www.jetbrains.com/idea/download/
Eclipse sometimes can produce such problems

Eclipse ADT version 21 plugin , fail to compile working workspace "no targets available” when everything correctly setup

I have problem with compiling workspace fully functional after Update to ADT 2.1 , after some eclipse restarts and cannot find any mention about it anywhere. I am running Mac OS X Mountain Lion and I also tried to use Eclipse installation coming bundled with latest ADT 21. Problem is still repeating. It seems to me as bug.
In Android preferences of Eclipse there is message “No targets available” even thou folder is correctly setup to correct SDK.
So it toke mi almost two hours to find working solution for this bug. I reinstalled everything tried to go back to ADT 20 and then accidentally upgraded tools and again was forced to update ADT to 21 that is failing for me…
Solution is simply to have two correct Android SDK folders and you have to point eclipse to other folder, apply, it loads SDK correctly than you can go back to SDK you actually use and everything works. Well till next restart and yo have to do it again . Thank you Android developers , each new big update , new big bug on osx :)
There is another option (from https://stackoverflow.com/a/14045656/4100), if you did disable the android plugin from running at startup, this will happen. Enabling it should fix the bug.

Missing all SDK Platforms

Couple of weeks ago I was working on android application. Everything was working fine. I have updated my eclipse with all the versions of android sdk. Starting from 1.* to 4.0.3. Today I opened my project to make some changes in that. And I found only 4.0.3 platform. And all my projects have hundreds of errors even my AVD is showing with red cross on it.
Can any one please tell me what is it? How come I miss my all installed sdk platforms?
Thanks in advance.
If you accidentally deleted the Android SDK folder it would stop all your code fro working. Try resetting up you path. In eclipse go to Window -> Preferences -> Android. Then browse to the SDK folder in the SDK location target textbox.

Eclipse: won't let me use Android SDK, wrongly claims my ADT is out of date

I'm developing for Android with Eclipse, and all was working well until yesterday. I used Ninite to update all my stuff, including JREs and everything (pro tip: do not do that), and it restarted my computer without asking in the middle of editing my workspace.
This caused all kinds of filthy problems, but now it all works, except for Android. I've updated Android SDK and the eclipse ADT, then when I try to tell Eclipse the SDK location, it gives this error:
This Android SDK requires Android Developer Toolkit version 14.0.0 or
above. Current version is 12.0.0.v201106281929-138431. Please update
ADT to the latest version.
Now, this is an outright lie. My ADT is version 14.0.something. I've tried Help>Check for updates, it says there are no updates. I've tried Help>Install new software...>Available Software Sites and removing the ADT repo, then reinstalling ADT, and it says it failed because I already have version 14.0.whatever.
How do I convince eclipse that my ADT is up to date??
I found the answer to the problem. (I'm using Helios, but it should work anyway)
Goto folder /Program Files(x86)/Eclipse/Plugins/ and make sure previous older versions of com.android.ide.eclipse.adt.package_##... are deleted (sometimes update fails to delete because of UAC). Keep the current desired version and complete the following.
Run Eclipse as administrator or disable UAC temporarily. (windows 7)
Go to Help → Install New Software.
On Work with: type https://dl-ssl.google.com/android/eclipse/ and press ENTER.
Wait for Eclipse to fetch the repository. An item named Developer tools will appear in the list.
Mark it for install, press Next and follow the steps to install the ADT tools.
When finished, it will ask to restart Eclipse. Make sure you do this.
When Eclipse restarts, all your Android SDK packages should show up again.
Dont forget to resume UAC if you need it.
An option is to manually download the ADT plugin (ADT archive) required. The page is, http://developer.android.com/sdk/eclipse-adt.html. The page reveals ADT 18 is available at http://dl.google.com/android/ADT-18.0.0.zip. The link is closer to the bottom page. I needed 17 although 18 was the latest, so I modified the download URL, changing 18 to 17.
Select Help → Install New Software → Add → Choose Archive and select the location of the downloaded ADT archieve file, Choose OK.
Select the components required and proceed as required. You may get a message that the software is already installed, proceed with the installation.
Hope this helps.
I had the same problem. My ADT in the eclipse was 8.x version. But my app required version 12 or more. So, I decided to upgrade both the Android SDK and ADT to the latest (at this time latest ADT is 17). I was able to upgrade the SDK but not the ADT. It always complained I got the versions already but I only had 8.x. The new SDK that I just upgraded would function only with ADT 14 and above. So, I had successfully broken my android development!!
The reason why I wasn't able to upgrade my ADT to the latest was because I was using Eclipse 3.5. The newer ADT versions require 3.6 or above. This small but key bit of information was really at the bottom of the error generated by Eclipse which required scrolling down (since only the top few lines of error were displayed). You typically wouldn't scroll down since these top few lines were followed by whitespace lines :). I did not scroll and I guess I wasted about a day trying to rectify this problem. But eventually I saw those 2 up/down arrows at the right of the dialog box and I scrolled down. There it clearly mentioned ADT 17 requires Eclipse runtime 3.6 and over.
So my solution was to find a suitable ADT that would work with Eclipse 3.5. Yes, tomorrow when I am in the mood, I shall upgrade to Eclipse 3.6 or 3.7 and the boat load of plugins I have :)
I've just upgraded my Android SDK version, and had exactly the same issue.
The 'Check For updates' Eclipse command failed because, for some reasons, Android Traceview failed to update.
My solution was to :
* Open Eclipse → Help → About Eclipse .
* Click Installation Details.
* Here select all the android related lines, and update them one by one, restarting eclipse each time.
And finally it worked ( even with Helios ) !
Best option is go to open eclipse ID
Then go to Help → About Eclipse >>
u will find the Installation Details button click on that
And now u can see the all anriod extension installed.
Select all or select one by one and just click the update button.
you will get the latest version from the net.
Hope these will help you all.
In Eclipse:
Help → Check for Updates.
Your ADT and SDK is not up-to-date yet and Eclipse is complaining about the right stuff...
Open Android SDK Manager from toolbar and update your SDK from there. It doesn't help if you are checking Eclipse updates. Because through Eclipse you cannot check SDK updates for Android.
Button looks like this :
I'm hearing a common issue is that newer Android ADK versions require newer eclipse versions. Colleagues who hit this say they installed Indigo in place of older Helios versions and were able to resolve the issue this way. I have not yet done the same myself.
To anyone else with this problem, my solution was just to delete the Eclipse folder, and download a new copy from scratch. I had to then re-download all plugins including adt, which worked this time round.

Categories

Resources