Member Avatar for azapovjednik

Hello all,

I need to do some simple project for school in java eclipse... so I went to android developer page and downloaded the adt-bundle for windows... I have 64 bit windows so I downloaded 64 version...

I start it and it gives me the error Android sdk content loader has encountered a problem parsesdkcontent failed

I searched and searched google but nothing helps:

I deleted android folder from users folder, I deleted workspace folder as well, stopped adb.exe from task manager... it just wont work...

I must point out that a couple of months ago I did download this adt bundle and it worked fine, but I deleted it.... and now I want to start anew... and now it gives me this error...

can anyone help?

thanks

Edited by peter_budo because: Moving to mobile development
  • 2 Contributors
  • 3 Replies
  • 464 Views
  • 22 Hours Discussion Span
  • Latest Post Latest Post by azapovjednik

Dani AI

Generated

Brief summary and likely causes. The Eclipse/ADT message "Android SDK Content Loader … parseSdkContent failed" usually means the ADT plugin could not parse either SDK metadata or AVD configuration. Common root causes are corrupted AVD/.ini files (bad entries in %USERPROFILE%.android), a mismatch between ADT and SDK tools, or the SDK files being unreadable/locked by permissions or another process. These are the failure modes that most people see for this exact error. (stackoverflow.com)

Why moving to another drive sometimes helps. When moving the bundle fixes the problem (as reported by ), likely explanations include Windows permission/UAC rules, a path that contains spaces or non-ASCII characters, or extremely long paths that trigger Windows limits. Those factors make files or metadata inaccessible to ADT or the SDK parser; creating a simple ASCII path on a local drive avoids them. See reports of non-ASCII/path problems and Windows MAX_PATH behavior. (stackoverflow.com)

Practical checklist (do these in order):

  1. Close Eclipse and stop adb (Task Manager or adb kill-server).
  2. Inspect and remove corrupted AVD files: back up then delete %USERPROFILE%\.android\cache, the offending *.ini and the avd folder; Eclipse/ADT will recreate clean AVD files.
  3. Make sure no process (Eclipse/SDK Manager/antivirus) is holding locks on the SDK folder; if an update failed, try running the SDK manager from the SDK tools folder as Administrator or use an unlock tool.
  4. Verify ADT <-> SDK-tools compatibility and update ADT or SDK tools if needed.
  5. Ensure Eclipse and the JVM bitness match (32-bit Eclipse needs 32-bit Java, 64-bit needs 64-bit). If needed, point Eclipse to a specific JVM using -vm in eclipse.ini. (stackoverflow.com)

Quick examples (Windows):

taskkill /IM adb.exe /F
rmdir /S /Q "%USERPROFILE%\.android\cache"
del "%USERPROFILE%\.android\*.ini"
mklink /J "C:\android-sdk" "D:\path\to\android-sdk"   (run elevated)

If the checklist does not help, reinstall the SDK tools (standalone zip) and update ADT, or put the SDK in a short ASCII path and reconfigure Eclipse's Android -> SDK Location. For environment-variable guidance (ANDROID_HOME / PATH) and Windows PATH editing, follow the standard Windows/Java setup steps. (stackoverflow.com)

References: StackOverflow threads linked above cover the specific error patterns and the common fixes described. (stackoverflow.com)

Recommended Answers

All 3 Replies

Member Avatar for peter_budo

Sorry to say, but hardly anyine does Android development on Windows machines down to various issues with configuration. Secondly Eclipse is such mess.

Try to isntall Android SDK from zip instead of automated installation (do not forget to modify your system path and ANDROID_HOME there). Aso I would recommend to use AndroidStudio or IntelliJ.

PS: I hope you have Java 6 32 bit installed and not something else

Member Avatar for azapovjednik

thanks peter,
unfortunately it is a school project and it has to be done in eclipse ...
I downloaded a zip file from this link: http://developer.android.com/sdk/index.html#download

what do you mean by modifying system path and ANDROID_HOME? could you be more specific? thanks

Member Avatar for azapovjednik

I solved it in a weird way... the previous adt-bundle folder I had in C: folder... and there I tried to put it again but it was giving me that content loader error...

this time I unzipped the folder to D: drive and now it is working without errors...

I wonder what happened...

thanks anyway

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.