NavHostFragment continues to intercept back button even when app:defaultNavHost is false [132077777]

Fixed

Bug

Status Update

No update yet.

Description

il...@google.com

created issue #1

May 6, 2019 05:49PM

Component used: Navigation
Version used: 2.1.0-alpha03

It seems like the work in

https://issuetracker.google.com/issues/111598096 in Navigation 2.1.0-alpha03 has caused a regression from previous versions when
- using app:defaultNavHost="false" or leaving the attribute out entirely
- Manually changing the primary navigation fragment as per

https://developer.android.com/guide/navigation/navigation-programmatic

Where the NavHostFragment / NavController continues to intercept back button events, basically treating the NavHostFragment as if it always is the defaultNavHost.

Comments

il...@google.com <il...@google.com> May 13, 2019 09:14PM

Accepted by il...@google.com.

ap...@google.com <ap...@google.com> #2May 13, 2019 10:07PM

Please include a sample project that reproduces your issue.

ap...@google.com <ap...@google.com> #3May 14, 2019 08:40AM

Marked as fixed.

This should demonstrate the issue:

https://github.com/zackjp/safeargs-default-values-test

Run the unit test:

https://github.com/zackjp/safeargs-default-values-test/blob/master/app/src/test/java/com/zack/safeargsdefaultvaluestest/DefaultValuesInActionsTest.java

ap...@google.com <ap...@google.com> #4May 14, 2019 06:19PM

Maybe it is the same as the other issue I listed? Different use case but same root cause?

il...@google.com <il...@google.com> #5May 14, 2019 06:20PM

Switching to Kotlin Safe Args fixed the issue, so seems like the same issue, just on the Directions side (vs the other which is on the Args side).

Issue 132077777