Fixed
Status Update
No update yet.
Comments
il...@google.com
il...@google.com
ap...@google.com
Please include a sample project using Navigation 2.4.0-rc01 that reproduces your issue.
il...@google.com
Thank you but this version can still be reproduced，here is the project that can be reproduced:
- enable the setting of "don't keep activity" in developer options.
- start app, click "About" button.
- press HOME button.
- click app icon in launcher again.
Description
Version used:android.arch.navigation:navigation-ui:1.0.0-beta01
Devices/Android versions reproduced on: any
Navigation to a fragment destination with SingleTop option breaks back stack. The issue was introduced in beta01 update in commit 45818ac652ba3a43b07f980cf22ab78be886d81d by Ian Lake <ilake@google.com> on Wed Jan 30 10:45:37 2019 -0800.
I believe that the root of the issue is unnecessary "+ 1" in line 25 of androidx.navigation.fragment.FragmentNavigator.java:
ft.addToBackStack(generateBackStackName(mBackStack.size() + 1, destId));
When navigation is performed in SingleTop mode, the last fragment is being replaced making back stack 1 frame smaller.