How do you know that the process is still running? I've never seen this behavior. It's the other way around. The app is updated so cleanly that it forgets scheduled alarms.
>From what I know I think that an upgrade is an uninstall (removing the alarms and the running process) and install. So besides old shortcuts pointing to an activity that might not be available in the new app, or stuff that your app created on the SD card (*), you should start from scratch, but keep what's in /data/data/yourapp/files/ (your dbs for example). I am happy to be corrected. (*) There doesn't seem to be any lifecycle event that the app is going to be uninstalled. Does anybody have a solution for cleaning up the SD card in such a case? On Tue, May 5, 2009 at 12:30 PM, David C <[email protected]> wrote: > > Hi, > > After different testing, I found an issue with the "update method" > when installing an application update. > > I developped "DilbertDroid", and a lot of people are saying that there > is missing some functionnality but the latest version published on the > market have this functionnalities. > > I suppose that when updating a application, the updater doesn't kill > the process related to the application but only update the application > files on phone. Result: the old application is still running until you > kill the process or reboot the system. > > I think it is not very professionnal to tell user to deinstall and > then reboot their phone in order to install an update. > > > David > > PS: My application doesn't have any service running > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
