At your request, Xav, I've narrowed down a way to produce this problem, and
written it up at http://code.google.com/p/android/issues/detail?id=14607.
String
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email
set the target in the run configuration to manual and try, this worked
for me for the .apk error .. and make sure the target name is same for
the AVD and the project
On May 24, 11:57 am, hao wei jik...@gmail.com wrote:
I have the problem too. And I tried to delete the marker then run it. The
I have seen this error message too, but I didn't have to modify
project settings or run configurations to make it go away. I can't
remember what I did, but it was probably:
1) clean project
2) close project
3) try again, if still fails: repeat 1 2 and then:
4) exit Eclipse and re-enter.
I can't
Sometimes there was an error, and for whatever reason the IDE kept it
listed even though the error has been fixed. If you look at the
Problems tab at the bottom of the IDE, you may find an error listed
that has been fixed. Right click that error, and hit delete.
On May 21, 3:59 pm, Ken H
try to delete R.java then it will generate a new one...maybe it will
be ok
On May 22, 6:59 am, Ken H hunt1...@gmail.com wrote:
Eclipse is showing an error (little red x next to my project name),
but there is no error shown in any files -- meaning there is no
corresponding x next to any
I have the problem too. And I tried to delete the marker then run it. The
msg of console is Could not find .apk file.
2010/5/22 Ken H hunt1...@gmail.com
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
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
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
Yes, exactly! I've had this happen before but was able to get rid of
it by toggling the build project (for some reason that worked). This
time it wouldn't go away.
I did just upgrade to the SDK for 2.2 though. Maybe that had something
to do with it. I don't know.
do some or all of these long
9 matches
Mail list logo
