if you see unparsed aapt error, look in the Console view. Normally Eclipse is able to parse the output of aapt (which is an external tool used during the build), and put error marker on the affected files. If, for some reason (like the devs working on aapt create an error msg in yet another format, and don't tell me) aapt fails to parse the error, it'll show the error in the console view so that you can at least see it.
If that happens please file a bug on http://b.android.com with the actual output taken from the console. thanks Xav On Fri, May 21, 2010 at 4:27 PM, Ken H <[email protected]> wrote: > Ok, I opened a Window > Show views > Problems, and it said something > about an "Unparsed aapt error(s)!..." whatever the devil that is. > > So I deleted it...and got the emulator up and running. What did I > actually do? Not worried, just curious? Thanks, by the way... > > Ken > > On May 21, 4:02 pm, Xavier Ducrohet <[email protected]> wrote: >> Look at the Problems view, it may be a project config issue. >> >> xav > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
