I made a very simple Activity which shows a simple ListFragment like below:
My Activity:
public class MyActivity ex
To give an explanation:
The framework creates the Activity and calls Activity.onCreate().
Activity.onCreate() will somehow attach to the FragmentManager to let it know about the hosting activity. Activity.onDestroy() will unregister it again.
Now, you extend Activity and override onCreate(). You make calls to FragmentManager without calling through toActivity.onCreate(). The whole registration logic explained above is not executed. The FragmentManager therefore does not know anything about the activity and assumes it has already been destroyed and generates the exception with the misleading error message.