Fixed
Status Update
No update yet.
Comments
se...@google.com
wk...@google.com
il...@google.com
I attach a project to reproduce the issue.
There are 2 buttons: one add a named fragment transaction (which you can remove with back) and the other navigate to another fragment using nav graph.
There are 2 buttons: one add a named fragment transaction (which you can remove with back) and the other navigate to another fragment using nav graph.
th...@gmail.com
You should be using childFragmentManager, not requireFragmentManager(). As of Alpha 04 and https://issuetracker.google.com/issues/111345778 , back button presses are automatically passed to the child FragmentManager of the active Fragment, allowing you to do whatever FragmentTransactions you want in that child FragmentManager (using Navigation or not).
We can improve the error message though.
We can improve the error message though.
wk...@google.com
Ah, of course I should....
shame on me.
Improving the error message will surely help fools like me :) thanks
shame on me.
Improving the error message will surely help fools like me :) thanks
Description
Version used: 1.0.0-alpha-01
Devices/Android versions reproduced on: -
Safe args are a great enhancement for navigation. A great addition to that would be being able to define nullability for arguments. An example for how this would look like:
<argument android:name="id" app:type="string?"/>
(note the ? for the type) - an alternative would be to have another attribute - e.g. app:required="false" to make it less tied to Kotlin. The generated Args and NavDirections class would have the Nullable/NonNull annotations.
This would make it very obvious which arguments are required and which are optional - especially in Kotlin.