tree cb7f3bad5e51416f02baa12c392189f23f767183
parent 8cf399b2e813234a1a603df3575c2dcdfa38dc9e
author Adam Powell <adamp@google.com> 1460411684 -0700
committer Adam Powell <adamp@google.com> 1460411684 -0700

Prevent duplicate loader onLoadFinished calls on config change

Support edition

Loaders report entering the started state in two places, once from
their host callbacks and once when moving into their host fragment's
starting state. In the former, we will also deliver load results if
we're finishing a retained cycle.

In practice, the individual fragment start happens first which clears
the report-next-start flag, then the finishRetain step sees that flag
is cleared and dispatches the finished load results again. Change
reportStart to only call onLoadFinished if we are not finishing up a
retain step.

Bug 28074512

Change-Id: I5300573a9f0efbc8cf5b45280cad5b23c70acd79