Fixed
Status Update
No update yet.
Comments
il...@google.com
Oh I forgot to mention that I thought it might be connected to this issue:
Default access
View
Expanded Access
--
--
--
Issue 147456890
When navigating Up after a deep-link on a calling app's stack, arguments and URI are dropped.
Bug
Description
When executing deep-links from another app to a Destination which has parent Destinations, the initial Activity may be put on the calling app's task stack. This allows a back-press to return to the calling app, and an 'up' press open the parent of the Destination in a new task.
In navigateUp(), when flow reaches the following line:
The newly-created task stack does not include any of the arguments that the initial Fragment destination were given. Fragment args will be empty, and the Activity will not include the original deep-link URL.
The original URI and arguments should be passed to the newly-created Activity and Destination Fragment.