IssueTracker

The sample project that produces the issue (as shown in BugVideo.mov) is available at:
https://github.com/ericmaxwell2003/issuetracker-131557151-fragment

I suspect that we're just not setting the default state to be capped at STARTED and you'd see the same oscillation with setUserVisibleHint(). We should just fix it for both cases though

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 97519ce890a194fd21c47696996f90ac00920868
Author: jbwoods <jbwoods@google.com>
Date:   Mon Apr 29 13:18:22 2019

    Allow reordering when calling setMaxLifecycle in FragmentPagerAdapter
   
    When FragmentPagerAdapter (or FragmentStatePagerAdapter) call
    instantiateItem(), instead of the new added Fragment just being capped
    at the STARTED state, it first goes to RESUMED, then returns to the
    STARTED state.
   
    This is caused because setMaxLifecycle is split into 2 separate Ops (a
    set maxLifecycleState and an unset maxLifecycleState). These Ops are executed
    separately and both change the Fragment state. There is no need to unset
    the maxLifecycleState of a Fragment when it is first added, so the unset
    Ops becomes redundant. Setting allow reordering to true allows the
    FragmentManager to remove the redundant unset Op. This means new
    Fragments are correctly capped at STARTED, without the need to go to
    RESUMED first.
   
    Test: confirmed in test app
    Bug: 131557151
    Change-Id: I92feb1eeb3cbb0156d2d59eb698547fd5f061e85

M       fragment/src/main/java/androidx/fragment/app/FragmentPagerAdapter.java
M       fragment/src/main/java/androidx/fragment/app/FragmentStatePagerAdapter.java

https://android-review.googlesource.com/953918
https://goto.google.com/android-sha1/97519ce890a194fd21c47696996f90ac00920868