IssueTracker

Component used: Navigation
Version used: 1.0.0
Devices/Android versions reproduced on: Google Pixel 2XL

I am developing an app by making use of Navigation Architecture Component and I am running into a strange behavior with at least one of the navigation actions I have defined(at least only one has caught my eye yet).

    <action
            android:id="@+id/action_loginFragment_to_dashboardFragment"
            app:destination="@id/dashboardFragment"
            app:enterAnim="@anim/slide_in_right"
            app:exitAnim="@anim/slide_out_left"
            app:popEnterAnim="@anim/slide_in_left"
            app:popExitAnim="@anim/slide_in_right"
            app:popUpTo="@id/nav_graph"
            app:popUpToInclusive="true" />

When this action is executed, it causes a brief recreate and destruction of LandingPageFragment which comes before LoginFragment.

Below I can paste a log that might make it easier to understand what issue I am facing.
The app went through a cold start when the log was produced and I went from A >> B >> C

2019-04-04 14:36:04.103 13457-13457/my.application.id E/AppName: LandingPageFragment onCreateView
2019-04-04 14:36:06.535 13457-13457/my.application.id E/AppName: LoginFragment onCreateView
2019-04-04 14:36:06.634 13457-13457/my.application.id E/AppName: LandingPageFragment onDestroyView
2019-04-04 14:36:13.676 13457-13457/my.application.id E/AppName: DashboardFragment onCreateView
2019-04-04 14:36:13.715 13457-13457/my.application.id E/AppName: LandingPageFragment onCreateView
2019-04-04 14:36:13.729 13457-13457/my.application.id E/AppName: LoginFragment onDestroyView
2019-04-04 14:36:13.866 13457-13457/my.application.id E/AppName: LandingPageFragment onDestroyView

the 5th and 7th lines of the logs reflect the anomaly. There is no UI glitch at all, but nonetheless, this is not an intended behavior I would assume and can lead to potential crashes in applications.