Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have an Android app that consists of about 20 activities. Whenever there is a crash in the process due to an uncaught exception or crash in a native routine and the user chooses to “Force close” the process, only the activity in foreground is finished and taken off the History Stack.
It is my assumption that when the process is killed, all the activities in the History stack should go down as well? What could be the issue here or am I missing something?
Anyone else observed this?
More accurately, all of the process’ activities in the task would go away.
You are assuming that when there is “an uncaught exception or crash in a native routine and the user chooses to ‘Force close'” that this kills the process.