Building to the Android device has been an annoying process for the last month or two:
Each morning, I have to do a random bunch of things to not get the
error. This may include deleting the APK file on my machine, restarting the phone, restarting unity, and sometimes even my machine. (It might be that not any of these things actually fixes the problem, but that it just randomly starts working).
Once I have got the APK on the phone, it works fine for the rest of the day.
This, morning, however, I have not been able to get the APK file on the phone at all. I went through the usual steps several time, without any luck. If I build with logcat running, it looks like there exists some file that must be "destroyed":
Here is a snippet from the log
This looks too scary for me to attempt to get my Unity build running. Is there a simpler way? As you can imagine, I am quite frustrated, since I cannot test my application at all on the device.
We found a solution; one that is so simple and obvious I am almost too ashamed to leave the question here.
We simply deleted the file through Windows Explorer. No terminal commands, no super user privilages, no replacing android command programs. :S
answered Jan 21 '11 at 09:36 PM
That's true. It really is that simple - if you know where to find that file ;) The file you have to delete is located under:
Motorola Milestone Android 2.2.1
answered Apr 19 '11 at 08:08 AM