Fixed
Status Update
Comments
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #2
Oh I forgot to mention that I thought it might be connected to this issue:
jb...@google.com <jb...@google.com> #3
Please provide a minimal sample project along with the minimal steps to recreate the issue in the project.
Description
Component used: Navigation
Version used: 2.3.5.
Devices/Android versions reproduced on: all
I'm facing an inconsistent behaviour when using the generated safe args as opposed to the deeplink strategy.
Say I have following navigation graph:
I have defined 2 ways to navigate to the
DeepLinkFragment
:action_home_dest_to_deeplink_dest
example://my-deelink-frag?myArg={myarg}
In the
DeepLinkFragment
I'm using thenavArgs()
function to de-serialize the incomingBundle
and show a simpleToast
message.When navigating with the generated safe args I can sent an empty string as the value for
myArg
. No problem.However, when navigating with an empty string as argument via the deeplink way:
I get following stacktrace:
Which is coming from the generated
DeeplinkFragmentArgs
codeAs a fix I could add the safe args .
android:defaultValue
.However I feel like this is a bug since it is possible with the