IssueTracker

Component used: Fragment Version used: 1.3.0-alpha06

When using setReorderingAllowed(true) (such as when using the Navigation Architecture Component), doing a replace() will cause the new fragment to go through onCreateView(), onViewCreated() and potentially up through onStart() and onResume() before the previous fragment is stopped.

This means that any values that are set on a shared view model (i.e., when returning a result) during one of those methods is immediately sent to the other fragment instead of waiting for the user to return to the previous fragment.

Ideally, the previous fragment should be stopped (but specifically not have its view destroyed) prior to the new fragment moving up through lifecycle methods.