Binding the task to the application class instead of the activity instance.Just canceling the task when the Activity is destroyed and restarting it when the Activity is created again.Letting the task survive and updating it with the new activity instance via onRetainNonConfigurationInstance.Disable orientation changes.(For sure not the way you should handle this.).So, I am looking for some kind of "best-practice" to avoid these errors and prevent AsyncTask from failing.
And as the instance of AsyncTask is connected to that activity, it fails and causes a "force close" message window.
AsyncTask is a great thing to run complex tasks in another thread.īut when there is an orientation change or another configuration change while the AsyncTask is still running, the current Activity is destroyed and restarted.
0 kommentar(er)
