Tuesday, July 6, 2010

Random droid error

While following my guide/tutorial reading I ran across the strangest error with the Droid SDK and eclipse. In case any of you also have a "compiling" error in eclipse that won't let you start up the droid emulator due to a "Unparsed aapt error(s)! Check the console for output" but you dont have any real coding errors you might want to consider just deleting that error message and re-running the application to compile.

It worked for me without any code/bug fixing. This took me a good hour before I figured googling the issue might be a good idea. So hopefully I'll save some of you an hour too.

No comments:

Post a Comment