Best IT Recipes

How to resolve Eclipse Android SDK error markers

After starting Eclipse, I received the message "Android SDK: troubleshooting error markers encountered a problem. Resolving error markers

+5
android eclipse
Jan 22 '14 at 4:33
source share
9 answers

Yes, I also came across this problem many times, and I had a very good solution, I think it will be useful to you,

Clean all projects in the workspace and restart Eclipse to resolve this problem.

Enjoy the coding :-)

+5
Jan 22 '14 at 4:38
source share

Cleaning up your projects is worth a try, but rarely solves the problem. Here is a simple solution you can count on to work.

  • From the Start menu, select Run ...
  • Enter cmd, click OK (to invoke the DOS prompt)

  • Go to the eclipse directory

    cd [location of your eclipse]

  • enter this command at the DOS prompt:

    eclipse -clean -refresh

  • The Eclipse splash screen appears. Be patient. Nothing seems to be happening, but in a few minutes you can use Eclipse again.

+7
Aug 24 '14 at 17:19
source share

I experienced two versions of this problem that have different solutions.

1.) Clear all projects in the workspace as described in other answers.

If it gets stuck while cleaning up a project because it never gets into this operation in the process queue, try the following steps.

2.) Make sure your workspace directory still contains the .metadata directory.

3.) Switch workspaces and then try to return. You may need to force close Eclipse during the switch.

4.) If all else fails, try manually deleting the .metadata directory, and then reinstall the workspace.

+6
Mar 30 '14 at 17:00
source share

This has happened to me many times. The solution to all projects is the solution. Sometimes you may need to close and reopen Eclipse.

+3
Jan 22
source share

I also found that running Eclipse without connecting devices goes past error resolution tokens. The devices I used are 4.4.2 if this helps.

+3
Apr 01 '14 at 17:24
source share

all other solutions did not work for me, so I just deleted all the .log files inside the [workspace] / folder . metadata strong> and it worked again!

+3
Aug 04 '14 at 9:32
source share

In my case, cleaning up all projects did not help. I deleted the .metedata folder and recreated the workspace. One of my Android projects contained bugs in the build path (Eclipse had not previously been detected). I added it as a general project and bug fixes.

If cleaning does not help recreate the workspace, this is the fastest way to find the real mistake.

+2
May 04 '14 at 13:21
source share

There are many solutions to solve this problem, but the Simplest solution is just clean and updates your eclipse as follows.

[ECLIPSE_PATH]>eclipse -clean -refresh

Example_

eclipse path on my system.

C:\Android_new_Setup\Android_setup_10.09.2014\adt-bundle-windows-x86-20140702\eclipse>eclipse -clean -refresh

If the problem has not yet been resolved, Capturing Eclipse on the Android SDK content loader will help solve this problem.

Hope this helps everyone. :)

+1
Feb 24 '15 at 5:57
source share

Go to the workspace folder and find any folder that is not listed in your Eclipse IDE. Delete these folders and run your IDE again. This should solve the problem.

0
Apr 11 '14 at 9:55
source share


More articles:


All Articles