IssueTracker

As per comment#94, this issue is covering all of the multiple back stack work across Fragments and Navigation. With this last change in comment#111, the work on the Fragment level has completed and the new saveBackStack(name: String) and restoreBackStack(name: String) APIs have been added to FragmentManager in snapshot build 7248696 of Fragment 1.4. I would still recommend waiting until the actual Fragment 1.4.0-alpha01 release, which will be accompanied with documentation around usage and restrictions (all of which have been thoroughly covered in the detailed descriptions in the changes above).

With the Fragment work complete, the implementation work on the Navigation side of multiple back stacks is next up - you'll continue to see changes added to this CL as that work continues.

As a reminder, that Navigation work includes:

• The generic Navigation API that will allow any Navigator (be it Fragments, Compose, etc) to support multiple back stacks
• Rework of the existing Navigators to support multiple back stacks out of the box
• The APIs in NavigationUI and other surfaces to allow you to easily opt in to using multiple back stacks

Also as mentioned before:

I'd ask that you hold your comments on the intermediate steps along the way as much of it will make more sense when taken as a whole once we release the first alphas (still planned for Fragment 1.4.0-alpha01 and Navigation 2.4.0-alpha01). Definitely expect a more thorough run through of how to use of these APIs via documentation, samples (including updating the NavigationAdvancedSample to use the new APIs), blog posts, videos, and everything else at that point and onward. Besides seeing each commit come through on this issue, we'll also make sure to point out when a first snapshot is available with working APIs for those of you who would like an early preview before the first alpha releases.

Again, please keep in mind the many people who get emailed for each comment on this issue - let's continue to keep this as a good channel for updates and not for general discussion or requests for additional progress updates. If you'd like to receive updates, please star the issue, not comment on it.

A question: with all due respect, are these automatic comments really necessary or useful? I'd like to keep my "star" on this issue, and know when it will be fixed. But the noise doesn't help. Thanks a lot!

Re #131 - yes, they are necessary. As stated multiple times and seen in the hotlists this bug is associated with, this will be fixed with Fragment 1.4.0-alpha01 and Navigation 2.4.0-alpha01, so if you're looking for only an update on when those are released and not for updates on the progress leading up to that point, you can use the AndroidX releases page and the RSS feed it has there.

With these last changes and snapshot build #7351514, we've completed all of the required changes to support multiple back stacks in:

• Fragments (i.e., without using the Navigation Component at all): this is an opt in change by using the new FragmentManager APIs of saveBackStack and restoreBackStack.

• The core Navigation Runtime: adds opt-in new NavOptions methods for restoreState and saveState and a new overload of popBackStack() that also accepts a saveState boolean (defaults to false).

• Navigation with Fragments: the FragmentNavigator now utilizes the new Navigator APIs to properly translate the Navigation Runtime APIs into the Fragment APIs by using the Navigation Runtime APIs.

• NavigationUI: The onNavDestinationSelected(),BottomNavigationView.setupWithNavController() and NavigationView.setupWithNavController() now use the new restoreState and saveState NavOptions by default whenever they would pop the back stack. This means that every app using those NavigationUI APIs will get multiple back stacks without any code changes on their part after upgrading the Navigation 2.4.0-alpha01.

• Navigation Compose: NavHost and the ComposeNavigator have also been updated to support saving and restoring the state by using the Navigation Runtime APIs. An example of using the restoreState+saveState APIs with a bottom nav can be seen in the BottomBarNavDemo.

All of these changes will be available in the upcoming Fragment 1.4.0-alpha01 and Navigation 2.4.0-alpha01 releases. (Note that Navigation Compose versioning has been merged into the rest of Navigation as per b/172823546).

That being said:

• there's a lot more documentation and samples that need to be updated. We'll be tackling as much of this as possible between now and the alpha01 release.
• As you may have seen, there's been a huge number of changes needed to make this happen across all levels. As such, please file separate bugs as you discover any edge cases that we need to handle and we'll make sure those changes are addressed in an alpha02 release.

I'd like to thank you for your patience and respectfulness in not spamming this issue with comments.

I'm also facing a couple of new issues. The first one is related to a transition crash:

    java.lang.IndexOutOfBoundsException: Index: 10, Size: 10
        at java.util.ArrayList.get(ArrayList.java:437)
        at androidx.fragment.app.FragmentTransitionImpl.setNameOverridesReordered(FragmentTransitionImpl.java:182)
        at androidx.fragment.app.DefaultSpecialEffectsController.startTransitions(DefaultSpecialEffectsController.java:665)
        at androidx.fragment.app.DefaultSpecialEffectsController.executeOperations(DefaultSpecialEffectsController.java:114)
        at androidx.fragment.app.SpecialEffectsController.executePendingOperations(SpecialEffectsController.java:294)
        at androidx.fragment.app.Fragment$3.run(Fragment.java:2760)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7656)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

MaterialContainerTransform is used here.

And the second one is related to a significant performance drop. It seems like the app is almost freezing for a fraction of a second on the bottom navigation stacks swap.