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

Might be related to

https://issuetracker.google.com/issues/118020865. BTW, I'm using 1.1.0-alpha01.

Project:

https://github.com/SUPERCILEX/Robot-Scouter/tree/2e3100276e5fe2cbad8a2cbb36303694e9f46bbd
Setup: ./gradlew setup

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

This is due to a bug in Fragment - using 1.1.0-alpha02 of Preference uses a newer Fragment dependency, and fixes this issue.

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

Assigned to il...@google.com.

Actually, I just checked and it still crashes using 1.1.0-alpha02.

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

Could you maybe upload a simpler project with reproduction steps? Or at least provide reproduction steps for the project you linked - Does it crash when using Preference 1.0.0?

This still seems suspiciously similar to

https://issuetracker.google.com/issues/120240628, which can not be reproduced with 1.1.0-alpha02 (following the reproduction steps in the first comment).

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 guys. I can also confirm that it still crashes using preferences 1.1.0-alpha02. I ran the barebones sample project included in

https://issuetracker.google.com/issues/120240628 on a Samsung Galaxy J2 Prime running Android 6.0.1.

If I use 1.0.0 version, the NPE issue will not appear. If I use any of the 1.1.0 alphas with/without fragments 1.1.0-alpha02, the NPE issue is there. This issue also exists for MultiSelectListPreference.

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

I also ran it on a Samsung Galaxy J4+ running Android 8.1.0, and it is the same story. There is no NPE issue using preferences 1.0.0, but using any of the 1.1.0 alphas with/without fragments 1.1.0-alpha02 will cause the NPE.