David Golombek wrote: > We could kill our app proactively, as soon > as we launch the ACTION_VIEW activity, but then we're left in a bad > state if the user aborts.
Why? In other words, what difference is there between: -- the user exits your application via back-button -- Android closes up your application to reclaim memory -- Android kills off your application's process to reclaim memory in a hurry -- you close up intentionally as part of the upgrade process If your concern is that you don't want to keep nagging the user about the new version if they expressly aborted the upgrade, write yourself a file/preference/database record indicating you've already told them before you launch them into the APK/market and close up shop. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in Germany, 18-22 January 2010: http://bignerdranch.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
