Thank you for sharing this. I have it implemented and working. However:
1) I install ver 1 of my app (working no problem)
2) I place ver 2 on the server. the app retrieves ver2 and saves to SD card and prompts user to install the new package ver2
3) ver2 installs and works as expected
4) Problem is, every time the app starts it wants the user to re-install version 2 again.
So I was thinking the solution was simply delete the APK on the sdcard, but them the Async task wil simply retrieve ver2 again for the server.
So the only way to stop in from trying to install the v2 apk again is to remove from sdcard and from remote server.
As you can imagine that is not really going to work since I will never know when all users have received the lastest version.
Any help solving this is greatly appreciated.
I IMPLEMENTED THE "ldmuniz" method listed above.
NEW EDIT: Was just thinking all me APK's are named the same. Should I be naming the myapk_v1.0xx.apk and and in that version proactivily set the remote path to look for v.2.0 whenever it is released?
I tested the theory and it does SOLVE the issue.
You need to name your APK file file some sort of versioning, remembering to always set your NEXT release version # in your currently released app. Not ideal but functional.
