I'm at a standstill in Eclipse due to an "Android Library Update" that never finishes. I tried restarting Eclipse, restarting my computer, deleting the .metadata folder under my Eclipse workspace, and several other shots in the dark. Under Window -> Preferences, I also already checked "Skip packaging and dexing (...)"
I have only two projects open: a small demo app and the Google Play Services Library linked to it. So the problem can't be too many projects, per this question.
Does anybody have any other ideas?
See the various steps in this post:
Eclipse hangs at the Android SDK Content Loader
One of the answers is mine (delete "workbench.xmi") which works for me the best. I find I have to do this every month or so.
If you are using windows, Open Windows Task Manager and serach for process named 'aapt.exe' and kill the same. This makes library update will start frome begining and it will continue further.
Please try the below:
Make sure that eclipse is not active. If it is active kill eclipse from the processes tab of the task manager
Open %USERPROFILE%/ on Windows or simply ~ on Linux/OS X (You can
locate this folder from the Desktop)
Go to .android folder (This may be a hidden folder)
Delete the folder cache which is located inside
.android folder
Delete the file ddms.cfg which is located inside
.android folder
Start Eclipse
I tried the above and it worked for me.
Hope it works for you as well.
Related
All of the sudden with no warning, any project I open in IntelliJ opens the .iml file only. If I go into Project Structure and set the .iml file to the root for the module, I can get the project view back, but then it says the SDK isn’t defined. If I do that, it works again but I have to reopen each folder under src folder (my java classes) individually, and when I exit and come back in I have to do it all over again.
This is happening for every single project I try to open, and I haven’t messed with any settings to cause this. Do you know what I can do to fix it? I am having to redefine the root module and sdk every time I open a project rather than it using the defaults as they are set, so each time I open my project I have to define it all over again because it has “forgotten” the module and SDK. I saw a fix that said to back up and delete the .idea folder but it didn’t help anything so I’ve added it back.
As of now, any project I open, new or old, has no defined module or sdk, even though just yesterday any project would open without a problem.
EDIT: If it helps I also use Pycharm, which is also by JetBrains, and I am having no trouble with it.
Wow Yes, "one drive for business " causes this behavior oddly.
Fix:
Moving the entire folder to outside of one drive has
fixed it,
after 2.5 hours of experiments by two of us!
-Henry
I disabled the "files on demand" feature in One Drive and that worked.
I've been getting this error message when I want to create a new project in NetBeans. There are two old answers for this question, Project Folder already exists and is not empty- Error in netbeans and Netbeans error: Project Folder already exists and is not empty. Not only they are addressed for NetBeans 7, but also they didn't work.
I tried:
deleting project directory,
deleting userdir under C:\Users..\AppData\Roaming\NetBeans,
deleting cache under C:\Users..\AppData\Local\NetBeans,
uninstalling and installing 8.0.2
updating JDK to 8.40
but none of them worked!
I really appreciate if you'd suggest a solution. Thanks already!
SOLVED: I uninstalled NetBeans from C directory and installed it to the D directory. Then while creating a new project I choose a directory under D. It works fine now!
There is a 99% chance that this is caused by your antivirus application.
You can check on allow file modification for NetBeans in your antivirus application.
I have Bit-defender total security 2018, so if you have it follow me:
Open Bit-defender
On protection tab click on (View features >)
Either you disable (Safe Files) or allow access for NetBeans.
By the way I think Bit-defender is blocking applications to access files on the C drive if I'm not mistaken, so that's probably why it worked for you when you put it on the D drive...
Go to Program Files, delete the NetBeans folder and reinstall it.
Go to C:\Program Files (x86) and delete NetBeans Folder And try to install it again
This might be because of your antivirus. I got the same problem sometime back.
I then switched off the DataLocker option in my antivirus app, after this the problem didn't recur.
I had the same problem when i was messing around with some templates, after undoing the edits and saving the error message stopped occurring.
When netbeans says project folder already exists, it isn't a total error. It still creates the project, it just ran into an error while re-creating one of the template files. If you have the original tab still open, all you have to do is undo to the point before you ruined some template.
Uninstalling and re-installing will fix the problem but i hope this knowledge helps.
I am using Android SDK Tools 23.0.2 with Android API 20 (L preview).
I have been having this error for some time:
parseSdkContent failed
.androidjava.lang.ExceptionInInitializerError
and I have looked at many other similar questions and tried their solutions to no avail.
They recommended deleting the /.android file in the user directory where my workspace is saved and restarting Eclipse. However this did not work for me.
parseSdkContent failed Could not initialize class android.graphics.Typeface
Android SDK Content Loader failing with NullPointerException
This error seems to be affecting my java code's ability to recognize the XML files it references. When I reference variables to components in the XML file, it does not recognize its existence, even though everything seems to be set up correctly.
Please let me know if any more information is needed.
I'd add a comment, but my rep isn't high enough...
Anyway, deleting .android folder worked for me. Your wording suggests you deleted then restarted Eclipse. Try:
Stop/Exit out of Eclipse
Delete .android
Restart Eclipse
I was using the 64 bit version of Eclipse ADT from this link https://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
and it was giving me issues on Windows 7 64 bit
I have now downloaded 32 bit version of Eclipse ADT from this link https://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
and now its working perfectly.
It might help others too.
I used the "switch workspace" option and created a completely new workspace. This new workspace gives me no problems.
I'd add a comment, but my rep isn't high enough... (just copied and paste here)
I was in the same problem and using Eclipse Luna + ADT Plugin, what I did was:
Exit Eclipse.
Delete .android folder from my home directory.
Delete .metadata folder from my workspace directory.
Also in my workspace deleted a folder called .remote (I don't remember exactly what was it's name, just deleted it).
Open eclipse, complete the ADT dialog, setup the Android SDK path, and check for eclipse updates.
If updates were done better you restart Eclipse before continuing.
Import my existing projects, (or create a new one).
Open a layout file (xml) to see if the error is gone.
Good luck!
I made the mistake of installing NetBeans as root:
sudo sh /opt/myDirectory/netbeansInstaller.sh
I installed it, launched it, and created a dummy project just to get familiar with it. Then I closed NetBeans and came back to it later on in the day. When I try to open/run NetBeans as my normal user, it launches with all sorts of error messages complaining about denied permissions.
So I uninstalled NetBeans completely using the uninstaller, and even deleted the project I created with it. I even deleted the installer itself out of my Downloads folder.
I re-installed NetBeans as normal user, and am still getting permissions errors. Now what happens is it launches, generates some error popups, and then freezes completely. I notice that it is still attempting to launch my deleted project by default!
Here is what I think is happening:
I run NetBeans as normal user
NetBeans has cached, somewhere, that my old project (which was created when I was using the old NB install as root) is the project to load at startup
It automatically complains that it can't load the project properly because I'm not root
It can't find my old project (because its deleted) and so it freezes in this "wait state"
Has anybody else ever had this problem? Any way to force NetBeans (perhaps from the terminal) to do a "clean load" where it won't attempt to load any projects? ANy other obvious solutions?
Thanks!
You could try deleting the .netbeans folders in the /root and in your home directory respectively. Netbeans maybe wants to read the /root/.netbeans folder for which it has no permission.
I am very new to Eclipse (Galileo, Eclipse IDE for Java Developers) and working on my first Android app, but have used SVN on many other kinds of projects and development. Last night I took my first crack at pushing the new source into a shared repository (at work) and then pulling it back down at home.
Based on an SO question/answer, I had ignored the bin and gen folders, but added everything else. When I got home, I had hoped it would be as easy as pointing eclipse to the newly downloaded source tree.
I tried setting the workspace (requested when eclipse started) to the precise folder holding all source. Nothing showed up. It was as if I were starting fresh regardless of all the source and files sitting in the workspace folder.
Then I thought maybe I needed to open a "project" file to get things rolling. Opening the .project file yielded the contents of that file in the XML editor of eclipse.
What am I missing here? Is the project metadata not stored in the source tree? Do I have to build project metadata up on every machine that gets a working copy of the source? Is this something wrong with my home Eclipse install? Can someone give me an overview of how they (successfully) do this?
You should be able to do it like you tried. Make sure you have the Android Development Tools (android eclipse plugin) installed along with the android SDK and make sure you set up ADT before you open the project.
Not checking in the bin directory makes sense to me, but I do check in the gen folder and don't have any problems.
Here is what I do to open a project from SVN if the source is already on the machine:
Open eclipse
Click on File->Import
Select General->Existing Projects into Workspace
Or you can also do this:
Open Eclipse
File -> Import
Select SVN -> Checkout Projects from SVN
Follow the steps to get from SVN