great. Luckily I only spent 15 minutes trying to solve before I found
your post.
-sfoye
On Mar 16, 6:57 am, Patrick Noffke <patrick.nof...@gmail.com> 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
No comments:
Post a Comment