IssueTracker

Fragments states could occur in a completly different order, if fragments are already in the pager adapter fragment list's.

FragmentMaxLifecycleEnforcer method's updateFragmentMaxLifecycle doesn't guarantee current item will be paused before new one will be resumed.

            for (int ix = 0; ix < mFragments.size(); ix++) {
                long itemId = mFragments.keyAt(ix);
                Fragment fragment = mFragments.valueAt(ix);

                if (!fragment.isAdded()) {
                    continue;
                }

                transaction.setMaxLifecycle(fragment, itemId == mPrimaryItemId ? RESUMED : STARTED);
                fragment.setMenuVisibility(itemId == mPrimaryItemId);
            }

Implamentation depends on key order and doesn't enforce current item's lifecycle before new one.
So if I have fragment A and B:
    - Moving from A to B will pause A and then resume B
    - Moving from B to A will resume A and then pause B