Unparsed aapt and Eclipse’s XML Build problem

This is mostly a post for my memory and to aid the searches.

Say you’re building an Android application using Eclipse, and you screw up your XML file, and then you FIX your XML file and try to run your app, but get an error window with Eclipse telling you that you have an error in your application and that it can’t launch and that you should check your console.

But there’s nothing in the console, and you have no errors.

Look in your Problems window and you’ll probably see an error that says something like this:

Unparsed aapt error(s)! Check the console for output.

It took me a while to figure this out, with a couple re-starts of Eclipse, before I accidentally stumbled onto the fact that if you simply delete the error message, you can build and run like normal.



Looking to figure out if this was my problem or Eclipse’s, I found Issue 10012 on the Android Google Code site.

I’ll check out the Eclipse bug system when I get a chance, because it seems like it might be an Eclipse issue rather than an Android SDK issue- could be wrong, but it seems like the aapt is fine from the Android Dev issue text.

Not sure this’ll help someone else, but it’ll at least help me remember.

One thought on “Unparsed aapt and Eclipse’s XML Build problem”

Comments are closed.