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

Question

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 t

Answer 1

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 :)