Provide a way to handle navigating back and forth between NavHostFragments embedded within other NavHostFragments (or if it's already available, document how to do) [120690961]

Fixed

Feature Request

Status Update

No update yet.

Description

je...@23andme.com

created issue #1

Dec 9, 2018 03:07AM

Component used: Navigation
Version used: 1.0.0-alpha08
Devices/Android versions reproduced on:

Assuming:
- Main Activity has a NavHostFragment, which navigates between Fragment A & Fragment B
- Main activity handles going back with onSupportNavigateUp
- Fragment B has it's own NavHostFragment, which navigated between InnerFragmentB1 & InnerFragmentB2
- Parent NavHostFragment navigates from A -> B (which starts with B1)
- Sub NavHostFragment navigates from B1 -> B2
- Press up: Sub NavHostFragment returns to B1
- Press up: Parent NavHostFragment returns from B to A

What's the proper way of handling these types of situations where we'd like the back button to handle backing out of Inner Fragments first and then Outer Fragments after?

Details here:

https://stackoverflow.com/q/53688934/1229936
Sample Code:

https://github.com/jeffreyfhow/NestedNavFragmentsTest

Comments

so...@gmail.com <so...@gmail.com> #2Dec 9, 2018 07:33AM

Project: platform/frameworks/support
Branch: androidx-main

commit 81120ca77c09c437775232585652b293ed572d45
Author: Clara Fok <clarafok@google.com>
Date: Thu Feb 29 17:29:44 2024

Paging to use common MainThread annotation

Test: ANDROIDX_PROJECTS=INFRAROGUE ./gradlew paging:paging-common:allTest
Bug: 327682438
Change-Id: I78f0d3cf36e3a3a9088e0698c351289cf2dbc1bf

M paging/paging-common/build.gradle
D paging/paging-common/src/commonJvmAndroidMain/kotlin/androidx/paging/MainThread.jvm.kt
D paging/paging-common/src/commonMain/kotlin/androidx/paging/MainThread.kt
M paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt

https://android-review.googlesource.com/2984997

il...@google.com <il...@google.com> #3Dec 10, 2018 05:58PM

Fixed internally and available in paging-3.3.0-alpha05

il...@google.com <il...@google.com> Dec 10, 2018 09:55PM

Accepted by il...@google.com.

il...@google.com <il...@google.com> #4Dec 14, 2018 12:05AM

Marked as fixed.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.paging:paging-common:3.3.0-alpha05
androidx.paging:paging-common-android:3.3.0-alpha05
androidx.paging:paging-common-iosarm64:3.3.0-alpha05
androidx.paging:paging-common-iossimulatorarm64:3.3.0-alpha05
androidx.paging:paging-common-iosx64:3.3.0-alpha05
androidx.paging:paging-common-jvm:3.3.0-alpha05
androidx.paging:paging-common-linuxx64:3.3.0-alpha05
androidx.paging:paging-common-macosarm64:3.3.0-alpha05
androidx.paging:paging-common-macosx64:3.3.0-alpha05

ka...@gmail.com <ka...@gmail.com> #5Dec 27, 2018 05:06PM

Re #4 - In my use case I have single activity and single (global) toolbar setup with it. So it doesn't make sense for my application to add additional toolbar for my nested fragments. I just want to work them with existing activity's toolbar. I would like to use nested fragments to use ViewModels shared with parentFragment. Can you consider supporting my use case?

Issue 120690961