Is System.exit(0) really that dangerous?
An application background service updates sqlite database. Therefore my
activities are becoming outdated. Activity intents also contain outdated
params so onCreate, onResume will crash the application. An easiest
solution is to restart whole application. I don't want to add IFs to all
onCreate, onResume methods in all activities to handle one special case.
I noticed that ACRA has following code executed after an exception has
been handled.
android.os.Process.killProcess(android.os.Process.myPid());
System.exit(10);
However many people discourage use of System.exit(0). Is System.exit(0)
really that dangerous for an Android application data integrity? Of course
my code will close the database before existing.