Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Note: I know alpha-02 has a fix for a biometric related leak:
However that change did not fix the leak reported here, as BiometricViewModel is still tied to the activity lifecycle no matter what and will hold the clientCallback reference until the activity is destroyed.
ap...@google.com <ap...@google.com> #3
Any news/possible for this issue?
jb...@google.com <jb...@google.com> #4
Can confirm that it still happens in 1.1.0-beta01
Description
We now have as dependency on the kotlin standard library and the FragmentStrictMode changes were new in this alpha so we can make them into Kotlin without breaking changes.