In the past, orientation changes and AsyncTask (and other long running background tasks) have not played well with each other. There’s always been the issue of knowing what tasks (or threads) are still running in the newly created activity (from an orientation change), and what to do when a task ends while an Activity isn’t attached.
Even with Fragments and the LoaderManager, this still seems to be a problem to me.
What is the preferred way these days, to manage arbitrary long running tasks and orientation changes? To know what tasks are running in the newly created activity. To make sure a task doesn’t try to deliver it’s information when an Activity isn’t attached.
Thank you
In my program I just put
in my activities in the manifest and be done with it. After 1 year I have had 0 problems.