Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Since this is happening in Tink, rather than in the AndroidX library, it would be best to open an
jb...@google.com <jb...@google.com> #3
an...@google.com <an...@google.com> #4
Tink is the library that does the heavy lifting in Jetpack Security.
And yes, potentially raising that issue with the Tink team directly could help.
il...@google.com <il...@google.com> #5
@4 Well why didn't Google offer it there? Crashes are far more important than warning logs...
Here, created it there too:
https://github.com/google/tink/issues/535
Here, created it there too:
Description
We should add documentation that explains how to properly handle code that was previously in an overwritten setUserVisibleHint(). (Code executed when passing in 'true' should be moved to onResume(), while code executed when passing in 'false' should be moved to onPause())