Fixed
Status Update
No update yet.
Comments
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.
ou...@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.
il...@google.com
ap...@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
il...@google.com
We've added a better error message in https://android-review.googlesource.com/861401 and this will be available in 1.0.0-alpha10.
sp...@google.com
Yes, Manifest Merger supports this. Pending CL adds test for this scenario.
Description
Version used: android.arch.navigation:navigation-ui:1.0.0-alpha05
Devices/Android versions reproduced on: any
I suppose it's no a bug, but just a wrong behavior.
If i have i custom scheme, like "com.example://" - this could not be used and inside framework http(s) will be appended.
NavDeeplink states that there is a scheme pattern, that should detect if there is any scheme before ":", but it fails if there is any dot in scheme. So any scheme that contains dots will fail. Only schemes with "-" are supported by now.
private static final Pattern SCHEME_PATTERN = Pattern.compile("^(\\w+-)*\\w+:");