Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Yes, this is correct. Having individual navigation graphs on each activities overrides or disallow up navigation to the main activity.
il...@google.com
I believe I have found the potential problem that is causing this:
// @ androidx.navigation.NavController
// line 124
// Now record the pop operation that we were sent
if (!mBackStack.isEmpty()) {
mBackStack.removeLast();
}
// We never want to leave NavGraphs on the top of the stack
while (!mBackStack.isEmpty()
&& mBackStack.peekLast() instanceof NavGraph) {
popBackStack();
}
the condition in while loop is never satisfied because of the above `if` statement above it has already removed the last item of the mBackStack (which was the NavGraph) and thus popBackStack() is never called again.
// @ androidx.navigation.NavController
// line 124
// Now record the pop operation that we were sent
if (!mBackStack.isEmpty()) {
mBackStack.removeLast();
}
// We never want to leave NavGraphs on the top of the stack
while (!mBackStack.isEmpty()
&& mBackStack.peekLast() instanceof NavGraph) {
popBackStack();
}
the condition in while loop is never satisfied because of the above `if` statement above it has already removed the last item of the mBackStack (which was the NavGraph) and thus popBackStack() is never called again.
Description
Version used: 1.0.0-beta01
When using an argType="reference" type, only valid resource values are allowed for the android:defaultValue - using @null or 0 doesn't work (both for Safe Args and at runtime).
It would be nice to have a default value available for resource types that would, at runtime, translate to a value of 0. Since would allow you to have optional resource IDs.