Fixed
Status Update
Comments
si...@gmail.com <si...@gmail.com> #2
This is affecting CameraView as well.
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #4
Hi. I've received your bug and will wait until 2020-01-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
si...@gmail.com <si...@gmail.com> #5
Hello,
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
si...@gmail.com <si...@gmail.com> #7
Bugjuggler:
il...@google.com <il...@google.com> #8
Hi. I've received your bug and will wait for b/146048690 to be fixed and then assign the bug to ericng@google.com.
si...@gmail.com <si...@gmail.com> #9
Bugjuggler: wait until next month
il...@google.com <il...@google.com> #10
Hi. I've received your bug and will wait until 2020-02-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
Description
androidx.navigation:navigation-*:2.6.0
and aboveThis commit b1ac7d6 introduced a regression in how the title is dynamically rendered, and more precisely how the
Bundle
containing parameters is accessed.Previously, it used the default
Bundle.get(key)
method:But after this commit, it now uses
Bundle.getString(key)
:Unfortunately, this breaks basic usage, with other types than
String
, sinceBundle.getString(key)
will returnnull
.Here is a very simple example:
Previously it would have correctly set the title to
"Album #42"
(for example).But since this update, it will render
"Album #null"
!