I don't know the details of your app, but every app in the Android market can be upgraded by the user while the app is running. During the upgrade process, the running instance of the older version would be shut down.
I've rarely seen any complaints that "the app is broken during upgrade from Android market", so I believe the upgrade process itself is sound. I think the main problem of your app is not the upgrading process, but rather it doesn't handle the android lifecycle model properly, and doesn't cleanly shut down. On Aug 25, 10:47 am, DaveG <david.golom...@flexilis.com> wrote: > On Aug 24, 12:34 pm, Hong <lordh...@gmail.com> wrote: > > > If you do: adb uninstall your.package.name.mainactivity, > > do you ever get any crash/error etc? > > > If not, the upgrade/installation process will uninstall your app cleanly. > > We do get crashes (that we're working on), but they don't matter > since our data files are deleted on uninstall, which is what we > want to ensure are not corrupted. > > > If onDestroy() is never called, try to do things in onStop(). > > I would assume onDestroy() will be called during un-installation process. > > I'll give that a try, thanks. > > > Other than that, you can potentially have a separate service running and > > check the state of your app, and also the activity of the installer/download > > activities, and clean up things accordingly. > > Yeah, we've been trying that and getting wierd results. If that's > really the > only way we can pursue it more. > > Thanks, > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
