I’m working on a team project. I included a
.jar file in Build Path and committed to SVN. When I updated code in my working directory, a new folder appears in Eclipse called “Android Dependencies”. If I let it be there, my program runs; If I remove it, my program reports a
Now how to fix this
Android Dependencies is a virtual folder where Eclipse shows what JAR files the project depends on. It’s not a physical folder; you won’t find it on your hard disk. And the folder is not checked in into Subversion.
Do not delete that folder. You will destroy your project.
To fix it, just revert to an older Subversion revision and check it in again.
For the people whose heart dropped when they read the comment that deleting the Android Dependencies virtual folder will destroy your project, there is an easy fix.
- Right click on the destroyed project
- Select “Android Tools > Fix Project Properties” in the dropdown
I hosed my project dependencies when trying to set up my git repo, and this is fixed it.
I’ve had a similar problem after setting up a git repo with my project.
The problem was that the appcompat import lost its folder reference.
If the ‘Fix Project Properties’ mentioned doesn’t work for you try this:
- Go to Project > Properties
- Go to the ‘Android’ tab
- Under ‘Libraries’, if there’s a red ‘X’ next to the appcompat folder, remove
it then hit ‘add’ and add it in again. The reference should show a
green tick now.
- Save and clean the project if needs be
If you also have marked project build target below API level 16 in the Android project properties, the error is going to come because prior to this level, there was no Android dependencies.