IssueTracker

Component used: Fragment

StrictMode is an Android system level feature for enabling the detection of potential problematic behavior and penalizing issues found (i.e., by enabling logging, throwing exceptions, etc.).

We should build the same type of infrastructure for Fragments so that developers can enable runtime checking for bad behaviors and validate that they (or libraries they depend on) aren't using deprecated APIs or known potential problematic behaviors.

Importantly, this should only be as a second line of defense behind deprecation warnings or Lint warnings to catch these issues at build time or to handle cases where third party libraries / dependencies are triggering these behaviors so that bugs can be filed against them.

We should support at least penaltyLog(), penaltyDeath(), and penaltyListener().

Given that we should maintain behavior compatibility, we should not add any enableDefaults() or detectAll() methods and instead have developers opt into exactly the detect***() methods they want. This should also remove the need for permit***() methods since they'll all default to off.

Ideally, this is something that developers can either:

1. Set globally via FragmentStrictMode.setDefaultPolicy(FragmentStrictMode.Policy)

2. Set on a specific FragmentManager (and its children FragmentManagers) via fragmentManager.setStrictModePolicy(FragmentStrictMode.Policy) (this would override the default policy)

This API shouldn't be made public until there is at least two detect***() calls added. These will be filed as separate issues.