Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Error with parsing Android sdk content and initializing java tooling in eclipse

Every time I open Eclipse, I get the following error messages:

Android SDK Content Loader: parseSdkContent failed java.lang.NullPointerException

Initializing Java Tooling An internal error occured during: "Initializing Java Tooling". java.lang.NullPointerException

Loading data for Android 2.2 Parsing Data for android-8 failed java.lang.NullPointerException

Loading data for Android 2.3.3 Parsing Data for android-10 failed java.lang.NullPointerException

Loading data for Google APIs (Google Inc.) Parsing Data for Google Inc.: Google APIs:8 failed java.lang.NullPointerException

See link for screenshot: http://i.stack.imgur.com/lhhQQ.png

(I am using OS X Lion, and Eclipse Helios)

First i read some posts saying that it was the AVD.ini file in the .android profile that was causing the trouble. I tried deleting all the entire .android profile folder as suggested in Android SDK Content Loader failing with NullPointerException. This didn't correct my problem.

I tried deleting the entire Android SDK folder, downloaded it again and installed a couple of Android versions through it. Still the same error messages...

To ensure that I didn't have any old plugins or something that were the issue, I uninstalled eclipse, downloaded it again and installed the Android plugin again. (So the plugin is up to date).

When I go into one of my Android projects, I get error messages on places where I acces resources by using the R file. Regular Java projects work fine, but all Android projects gets small red boxes with white crosses on them. I have been searching for a solution to this problem since yesterday, but at this point I'm completely qlueless and would appreciate any help I can get!

like image 362
Njaal Gjerde Avatar asked Apr 13 '12 12:04

Njaal Gjerde


1 Answers

Close all open projects and exit Eclipse. Now you can open Eclipse without getting the error. Start opening your projects one by one to find which one causes the problem. This is most likely because you deleted a Device profile inside the AVD manager.

like image 62
slott Avatar answered Oct 30 '22 21:10

slott