IssueTracker

I'd like to add that this automatic removal of the NavGraph at the top of the stack is also making it hard for me to implement proper lateral top-level navigation.
A practical case where this kind of navigation happens is with a Material Design bottom navigation bar, where I have a NavHost above the bottom bar.

Given this navigation scheme:
A - B   (top-level)
     B1 (first sub-level)

When starting the Activity, the back stack is
0. A
1. NavGraph

If I wanted to navigate to B laterally, I would do:
navController.popBackStack(R.id.navGraph, false)
navController.navigate(R.id.B)

But the resulting back stack is:
0. B

Now, navigating between top-level destinations actually works (though popBackStack returns false); the problem arises again if I navigate to B1:
0. B1
1. B

When navigating from B1 to a top-level destination like A, the stack becomes:
0. A
1. B1
2. B

That is, A is not a top-level destination in the back stack: if I press back from A, I intend to exit the app, but I'm taken back to B1.

It would be nice to have a fixed reference to the bottom of the stack. Right now I'm working around this with a horrible ` while (navController.popBackStack()) continue`.

Is this going to be fixed?

I have the same issue with a setup as follows:

Navigation graph.

    <navigation xmlns:android="http://schemas.android.com/apk/res/android"
        xmlns:app="http://schemas.android.com/apk/res-auto"
        xmlns:tools="http://schemas.android.com/tools"
        app:startDestination="@+id/startupGraph">

        <navigation
            android:id="@+id/startupGraph"
            app:startDestination="@id/launcher_home">
            <fragment
                android:id="@+id/launcher_home"
                android:name="com.example.android.codelabs.navigation.MainFragment"
                android:label="@string/home"
                tools:layout="@layout/main_fragment" />
        </navigation>

        <navigation
            android:id="@+id/homeGraph"
            app:startDestination="@id/flow_step_one">
            <fragment
                android:id="@+id/flow_step_one"
                android:name="com.example.android.codelabs.navigation.FlowStepOneFragment"
                tools:layout="@layout/flow_step_one_fragment" />
            <fragment
                android:id="@+id/flow_step_two"
                android:name="com.example.android.codelabs.navigation.FlowStepTwoFragment"
                tools:layout="@layout/flow_step_two_fragment" />
        </navigation>

    </navigation>
   
MainFragment.

        override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
            super.onViewCreated(view, savedInstanceState)
             view.findViewById<Button>(R.id.navigate_dest_bt).setOnClickListener{
                 Navigation.findNavController(it)
                         .navigate(R.id.homeGraph, null, NavOptions.Builder()
                                 .setPopUpTo(R.id.startupGraph, false)
                                 .build())
             }
        }

FlowStepOneFragment.

        view.findViewById<View>(R.id.next_button).setOnClickListener {
            Navigation.findNavController(it)
                    .navigate(R.id.flow_step_two, null, NavOptions.Builder()
                            .setPopUpTo(R.id.flow_step_one, true)
                            .build())
        }
    }
}

Causes the following error:

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.example.android.codelabs.navigation, PID: 12579
    java.lang.IllegalArgumentException: Navigator androidx.navigation.fragment.FragmentNavigator@d70ec6f reported navigation to unknown destination id com.example.android.codelabs.navigation:id/flow_step_two

The original issue was fixed as a result of https://android-review.googlesource.com/833717 and a number of other internal changes and that will be available in alpha08.

Discovered another issue when doing this specific set of navigation actions, so leaving this open until that part is also fixed.

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

commit d3507cb9dab82264070c72a37dbde1dfb43ef578
Author: Ian Lake <ilake@google.com>
Date:   Tue Dec 04 14:24:32 2018

    Split pop and dispatch logic
   
    When using popUpTo, navigate() would
    internally call popBackStack(), resulting
    in additional dispatch calls to
    OnDestinationChangedListener before the
    navigate() operation itself was done.
   
    By separating the logic, we can ensure that
    we don't prematurely remove NavGraph destinations
    that should still exist after the navigate()
    operation and that developers only see a
    single final OnDestinationChangedListener callback.
   
    Test: new test
    BUG: 113611083
    Change-Id: Ib63e4156521259a945ffecf679ccb404ac192017

M       navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
M       navigation/runtime/src/androidTest/res/navigation/nav_nested_start_destination.xml
M       navigation/runtime/src/main/java/androidx/navigation/NavController.java

https://android-review.googlesource.com/840996
https://goto.google.com/android-sha1/d3507cb9dab82264070c72a37dbde1dfb43ef578

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

commit fd35a469cabd33509e1d90c57561e33be03a0dd8
Author: Sumir Kataria <sumir@google.com>
Date:   Tue Sep 18 13:11:51 2018

    Prevent potential foreign key constraints in AlarmMgr.
   
    This change is an addition to the one for JobScheduler:
    https://android-review.googlesource.com/c/platform/frameworks/support/+/758783
   
    Also, this change fixes a potential issue where handleScheduleWorkIntent
    was not being executed inside a transaction as it should.
   
    Bug: 114705286
    Test: Added and ran tests.
    Change-Id: Ica1e54e3e9d43d52e11731f3a5727433aac0f622

M       work/workmanager/src/androidTest/java/androidx/work/impl/background/systemalarm/SystemAlarmDispatcherTest.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/CommandHandler.java

https://android-review.googlesource.com/760504
https://goto.google.com/android-sha1/fd35a469cabd33509e1d90c57561e33be03a0dd8

Fixed in alpha09.

It is happening again on 2.7.1 version
 
`implementation 'androidx.work:work-runtime-ktx:2.7.1'

We have following gradle version, it is impacted heavily

Gradle: androidx.work:work-runtime:2.7.0@aar
Gradle: androidx.work:work-runtime-ktx:2.7.0@aar
Gradle: androidx.work:work-rxjava2:2.7.0@aar

Attachment: Impacted Users and session in a week
This issue has 16,025,903 crash events affecting 55,770 users

Stack Trace:

Fatal Exception: android.database.sqlite.SQLiteConstraintException: FOREIGN KEY constraint failed (code 787 SQLITE_CONSTRAINT_FOREIGNKEY)
       at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount(SQLiteConnection.java)
       at android.database.sqlite.SQLiteConnection.executeForChangedRowCount(SQLiteConnection.java:890)
       at android.database.sqlite.SQLiteSession.executeForChangedRowCount(SQLiteSession.java:756)
       at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:66)
       at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1920)
       at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1841)
       at androidx.sqlite.db.framework.FrameworkSQLiteDatabase.execSQL(FrameworkSQLiteDatabase.java:265)
       at androidx.work.impl.WorkDatabase$2.onOpen(WorkDatabase.java:167)
       at androidx.work.impl.WorkDatabase_Impl$1.onOpen(WorkDatabase_Impl.java:113)
       at androidx.room.RoomOpenHelper.onOpen(RoomOpenHelper.java:136)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onOpen(FrameworkSQLiteOpenHelper.java:201)
       at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:427)
       at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:316)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:151)
       at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:112)
       at androidx.room.RoomDatabase.inTransaction(RoomDatabase.java:706)
       at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.java:483)
       at androidx.work.impl.model.WorkTagDao_Impl.getTagsForWorkSpecId(WorkTagDao_Impl.java:93)
       at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:135)
       at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:923)

i met issue too:  FOREIGN KEY constraint failed (code 787 SQLITE_CONSTRAINT_FOREIGNKEY)