Deep linking with multiple nested nav graphs doesn't correctly create the full backstack [214383060]

Fixed

Bug

Status Update

No update yet.

Description

el...@atomicmedia.co.uk

created issue #1

Jan 13, 2022 06:12PM

Component used: Navigation
Version used: 2.4.0-rc01
Devices/Android versions reproduced on:
Pixel 6 / Android 12

In the example project I have the following nested nav graph structure:

nav_graph{ startDestination=home
home {...}
list { startDestination=leaderboard
leaderboard
exampleNestedGraph { startDestination=exampleFragment
exampleFragment - deepLink="

example.com/user/{userName}"
userProfile - deepLink="

example.com/user/{userName}/details"
}
}
form {...}
}

Following the deep link:

example.com/user/Profile%202/details deep links to the userProfile Fragment as expected.

Then clicking back pops to the exampleFragment

Expected: Clicking back again takes the user to the leaderboard fragment, then clicking back a final time takes the user back to the home fragment.

Actual: Clicking back takes the user to the home fragment, skipping the leaderboard fragment.

I've also updated the bottomNavView_DeepLink_HandlesIntent_BackGoesToList test to test this case

It looks like this was introduced with

https://cs.android.com/androidx/platform/frameworks/support/+/9fc6ccd6e1759d75a8b72f49cedd359e87ba2f99

screen-20220113-175001.mp4

19 MB

Download

NavigationAdvancedSample.zip

366 KB

Download

Comments

jb...@google.com <jb...@google.com> Jan 21, 2022 01:23AM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #2Jan 25, 2022 09:19PM

Last Action:
2022-01-19 11:01:47,579 [ 43614] INFO - manager.EmulatorProcessHandler - Emulator: /home/ghost/Android/Sdk/emulator/emulator -netdelay none -netspeed full -avd Pixel_API_31
2022-01-19 11:01:47,600 [ 43635] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-01-19 11:01:47,698 [ 43733] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library /home/ghost/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
2022-01-19 11:01:47,760 [ 43795] INFO - manager.EmulatorProcessHandler - Emulator: qemu-system-x86_64: -chardev socket,port=45697,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:45697: Name or service not known
2022-01-19 11:02:27,813 [ 83848] INFO - rationStore.ComponentStoreImpl - Saving Project(name=armino_rents, containerState=COMPONENT_CREATED, componentStore=/home/ghost/StudioProjects/armino_rents)KotlinCommonCompilerArguments

jb...@google.com <jb...@google.com> #3Jan 25, 2022 09:20PM

Marked as fixed.

please run emulator with the following options and post the output here, thanks!
/path/to/emulator -verbose -show-kernel -avd <avename> -feature -ModemSimulator

the above command line will not use modem, just to see if it is related.

wb...@gmail.com <wb...@gmail.com> #4Feb 2, 2022 09:13AM

Yes,it worked.

Attaching the log below.

jb...@google.com <jb...@google.com> #5Feb 2, 2022 04:59PM

I'm getting the same error on my Ryzen 1800X on OpenSUSE Tumbleweed:

"qemu-system-x86_64: -chardev socket,port=38379,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:38379: Name or service not known"

Adding the "-feature -ModemSimulator" flags worked around the issue for me.

wb...@gmail.com <wb...@gmail.com> #6Feb 3, 2022 07:40AM

Hi truefalsetrue101@, could you try look at your /etc/hosts file on your machine? On my machine, it looks like

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost

If ::1 localhost is missing, that probably explains why "Name or service was not known".

Issue 214383060