Try: 1) Refreshing the project, and rebuilding.
2) Cleaning the project, and rebuilding. 3) closing and reopening the project, and rebuilding 4) deleting the project (but not deleting the files -- that's a checkbox on the project deletion confirmation dialog), and re- importing it as an existing project, and cleaning and rebuilding. 5) Delete the project, delete the .project and .classpath files in the project, and create a new project using your files as existing sources. 6) Creating a new workspace, importing the project, cleaning, and rebuilding. 7) Reinstalling Eclipse, creating a new workspace, importing the project, cleaning, and rebuilding. You shouldn't need to go beyond #4. #5 through #7 will cause you to lose various of your settings, so they're desperation moves, and since other projects work, I doubt these will fix this problem. On Apr 9, 12:07 pm, Eric Carman <[email protected]> wrote: > A little more information.... > > This seems to only occur with one of my apps in the workspace. I have > another with the same minSDK/targetSDK combo and it compiles and runs > just fine. > > I've switched the targetSDK to a couple of different choices, but > nothing seems to affect this error. I'm not showing any warnings or > errors in any of the source/xml files. > > I've backed out a bunch of changes I made yesterday just to see if > anything was causing this and so far, nothing. > > If you have a needle in any proverbial haystack that I could try, I > would appreciate it. > > Best Regards, > Eric -- 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 To unsubscribe, reply using "remove me" as the subject.
