Re: What state does "force stop" leave my application in?

[Rudolf Hornig]

Kills the process. Nothing remains, except the state the app has previously written out as files in the app's data directory.

On Monday, December 3, 2012 11:11:37 AM UTC+1, Richard Schilling wrote:

I see a lot of discussion about why you can't detect when "Force Stop" is pressed by the user.  And, that all makes sense. 

What I don't see is the specific answer to this question: When the user opts to use the "Force Stop" button, what state is the application left in?  What cleanup is the OS doing for the application?

Thanks.

Richard

[Kristopher Micinski]

Basically very little, which is why we dislike that it happens so much.

Detecting that someone has forced stopped your application is not
something that should be endorsed either: as it gives the impression
that your app could restart itself. (Which shouldn't be able to
happen, once the user kills your app it should be gone.)

kris

On Mon, Dec 3, 2012 at 5:11 AM, Richard Schilling <coder...@gmail.com> wrote:
> I see a lot of discussion about why you can't detect when "Force Stop" is
> pressed by the user. And, that all makes sense.
>
> What I don't see is the specific answer to this question: When the user opts
> to use the "Force Stop" button, what state is the application left in? What
> cleanup is the OS doing for the application?
>
> Thanks.
>
> Richard
>

> --
> You received this message because you are subscribed to the Google Groups
> "android-platform" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-platform/-/Rt-4e3XPipkJ.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-platfo...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-platform?hl=en.