Fixed
Status Update
No update yet.
Comments
il...@google.com
il...@google.com
ap...@google.com
I've confirmed that this is fixed in alpha08 as a result of https://android-review.googlesource.com/833717 and a number of other internal changes. Once it is released, please let me know if this fixes your issue.
The second issue of hitting two things at a time is not an issue with Navigation, but an issue with Fragments not canceling click events when stopped, causing the second click event to happen even after the first navigate() operation starts.
This is fixed in AndroidX Fragments 1.1.0-alpha01 or higher as per the release notes:https://developer.android.com/jetpack/androidx/androidx-rn#2018-nov-fragment
The second issue of hitting two things at a time is not an issue with Navigation, but an issue with Fragments not canceling click events when stopped, causing the second click event to happen even after the first navigate() operation starts.
This is fixed in AndroidX Fragments 1.1.0-alpha01 or higher as per the release notes:
il...@google.com
Unfortunately, Navigation 1.0.0-beta02 was pushed just a few hours before you reported this issue. It has been fixed internally and it'll be available in the next release!
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.