NavController.setGraph does not reset back stack [111450672]

Fixed

Bug

Status Update

No update yet.

Description

jf...@gmail.com

created issue #1

Jul 16, 2018 02:59AM

Library name: Navigation
Library version: 1.0.0-alpha03

When setting a new NavGraph to NavController, the back stack is not resetted.
From the documentation, "Any current navigation graph data will be replaced."
If a NavGraph is already setted then the back stack containts the default destination. In calling NavGraph.setGraph(NavGraph) and in the new graph, the destination is different, then the new destination is not displayed because back stack is not resetted.
Is it expected feature or not?

Comments

il...@google.com <il...@google.com> #2Jul 17, 2018 06:16PM

Is there any updates? This is a big problem!

ha...@googlemail.com <ha...@googlemail.com> #3Jul 17, 2018 08:41PM

Hi there - could you provide more context on the issue & a sample project to reproduce? Database locked exceptions are quite difficult to pinpoint without a repro project. Thanks!

il...@google.com <il...@google.com> #4Jul 23, 2018 11:04PM

Assigned to il...@google.com.

Hi. It is reproduceable on some users by using this code:

suspend fun <R> MyDatabase.workaroundWithTransaction(block: suspend TransactionScope<R>.() -> R) {
    useWriterConnection {
        it.immediateTransaction(block)
    }

    // TODO: Temporally fix https://issuetracker.google.com/issues/340606803#comment2
    // Manually triggers invalidation
    invalidationTracker.refreshAsync()
}

bo...@gmail.com <bo...@gmail.com> #5Sep 17, 2018 01:24PM

Maybe it is about this? https://android-review.googlesource.com/c/platform/frameworks/support/+/3114928

I am not sure.

il...@google.com <il...@google.com> Jan 11, 2019 01:22AM

Accepted by il...@google.com.

il...@google.com <il...@google.com> #6Jan 11, 2019 10:59PM

Marked as fixed.

Hi. Please merge the pull request. This is big problem!

lb...@gmail.com <lb...@gmail.com> #7Sep 6, 2024 10:29PM

Hi. Is there any updates on this problem?