You haven't found it, because it doesn't exist :-)
When the OS or a 3rd party app kills your process, it *kills* it
forcefully. And if your app's process is killed your app no longer runs and
obviously can't process any callbacks/lifecycle-events, etc.
On Sunday, March 24, 2013 3:47:17 AM
Actually you should take his suggestion, as it can also solve your issue.
Obviously something is wrong when the app is relaunched, you can use that
missing information to understand you need to restart your app (i.e, if
it crashes because the user login details are missing, just reset the app
The question is not limited only about force close errors. It is more about
the sudden death of the application which can happen because of so many
reasons. In which I want to handle Force close when user goes to the *Settings
- Applications - my App* and clicks *Force Close* and When some task
I would focus on your force close error and fix that one instead of trying
to work around other apps.
On Thursday, December 27, 2012 12:02:06 AM UTC-6, Amit Dwivedi wrote:
In my App I have several activities which are obviously related to each
other. Whenever I am on some activity and the
The link you give is all very good background on tasks and the activity
stack (a.k.a. 'back stack), but how does that help the OP understand what
is different in third-party task killers and why it has such a different
effect on his program? If the third party task killer does it by killing
Read this
http://developer.android.com/guide/components/tasks-and-back-stack.html
On Thursday, 27 December 2012 11:32:06 UTC+5:30, Amit Dwivedi wrote:
In my App I have several activities which are obviously related to each
other. Whenever I am on some activity and the user kills my app by
6 matches
Mail list logo
