Fixed
Status Update
No update yet.
Comments
jb...@google.com
ap...@google.com
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.
Description
When using FragmentStrictMode, it might not be possible or prudent to fix all violations at once.
It would be convenient to let developers build up their allow list of Fragment class name + Violation class name pairs that could serve as the baseline for their app.
This would allow developers to enable more strict penalties for new violations while slowly working down the set of known violations, effectively allowing them to stop the bleeding and avoid regressions as new features are developed.