I started noticing this problem about two weeks ago, but it's hard to nail 
down. I would change something in my code, wait for eclipse to finish 
building, deploy to my emulator or device, and proceed to step on the new 
code. I'd see no change and would then check my logs to see what happened: 
whatever change I just made wasn't in the code on my emu/device. I have 
checked the console output, and it uploaded a new APK. I would try and 
redeploy from Eclipse, and it says the APK is already installed, no need to 
reinstall.

The only way I have found to fix this issue is to either close eclipse 
entirely, or clean the project. Doing either of these things completely 
defeats the purpose of having a build automatically option, and in general I 
choose to restart eclipse because many times ADT will trip over itself while 
cleaning - see one of the many posts about not finding the "gen" folder - 
ugh...

Has anyone else had this problem with ADT? Does anyone from either the 
community or the ADT team have an explanation/workaround/fix? This sometimes 
happens around 20 times a day, which is really quite annoying.

-- 
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

Reply via email to