Status Update
Comments
il...@google.com <il...@google.com> #2
Can you explain your use case?
b9...@gmail.com <b9...@gmail.com> #3
When there is an intent comes in Ui side, e.g. notification, broadcast, onNewIntent(intent), I want to call navController.onHandleDeepLink(intent) to navigate to Fragment, just like navController.navigate(...), so I think that this method should offer the same parameters as navigate(...) such as NavOptions, so that I could navigate to a destination seamlessly either through navigate(...) or onHandleDeepLink(intent).
il...@google.com <il...@google.com>
jb...@google.com <jb...@google.com>
jb...@google.com <jb...@google.com> #4
In the Navigation 2.1.0-alpha03 release we introduced navigating within an app by deep link uri: https://buganizer.corp.google.com/issues/110412864 . That api has an overload that allows the passing of NavOptions along with the destination uri.
For the foreseeable future, we would prefer to use navigate by uri to handle adding a custom animation.
Marking this as a duplicate of the other bug.
For the foreseeable future, we would prefer to use navigate by uri to handle adding a custom animation.
Marking this as a duplicate of the other bug.
Description
I hope there is a way to assign animation via NavOptions when navController find a destination from deep link.