Fixed
Status Update
No update yet.
Comments
il...@google.com
il...@google.com
ap...@google.com
This is because a PendingIntent doesn't use the extras/arguments to compare 2 intents, so each notification actually use the same pending intent, and the extras arguments are updated (PendingIntent.FLAG_UPDATE_CURRENT).
If you have a <deepLink> element in your destination, you should use the Uri to navigate to it.
```
<deepLink app:uri="http://www.example.com/users/{id} ">
Intent i = new Intent(Intent.ACTION_VIEW, Uri.parse("http://www.example.com/users/42 ");
```
If you have a <deepLink> element in your destination, you should use the Uri to navigate to it.
```
<deepLink app:uri="
Intent i = new Intent(Intent.ACTION_VIEW, Uri.parse("
```
il...@google.com
This has been fixed internally in https://android-review.googlesource.com/861068 and will be available in Navigation 1.0.0-alpha10. Navigation now uses both the destination ID and the arguments to build a unique requestCode for the PendingIntent, ensuring that you can create multiple PendingIntents to the same destination.
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.