IssueTracker

Component used: Fragment

Allow developers to detect when they are reusing a fragment instance after it was previously removed from a FragmentManager (i.e., that initState() was called).

Ideally, this should also change the require***() methods to change their error message based on whether the fragment was never added (the current error message) or if it was previously added but has since been removed (a new error message).

This would probably have to hook into both the FragmentTransaction methods for adding a fragment (to provide better stack traces) as well as in the internal addFragment() to ensure that Fragments that were removed as part of an inflight transaction are properly caught.