Thanks, only 20 minutes lost here. I hadn't even thought about right- clicking the error message.
On Mar 16, 3:57 pm, Patrick Noffke <[email protected]> wrote: > Hi all, > > I found some old posts on this problem, and I was having a similar issue, so > I thought I'd share what I learned. > > I was getting this error after modifying an XML file, and I was unable to > start a debug session until I fixed the problem. It seems if there are > errors that cause aapt to fail, eclipse can get in a state where it doesn't > know when the problem gets fixed. Deleting R.java did not work for me. > What I ended up doing after I fixed the XML file is right-clicking on the > error message in the Problems view, and deleting the error. Then modify > some files to force a rebuild and you should be okay. > > I found it helps to turn the android log level to Verbose (Preferences -> > Android -> Build). This led me to know that once I fixed the XML file, aapt > was happy, but eclipse was not. > > Hopefully this will save someone else the 3 hours I burned trying to figure > it out! > > Patrick -- 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
