Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
commit b9b1326edfe38588a9882e1ee624798966c5686a
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed Oct 06 16:49:53 2021
Clear focus on Fragments animating out
Since moving to the new state manager, fragment now explicitly handle
focus where in the old world they could ignore it altogether. This
change has the side effect that other things affected by focus (i.e.
soft keyboard input) are affect as well. In particular when we
requestFocus we update the input request, but since we never clear it
users have to manually remove the input.
When we are animating a fragment view out, since we will no longer be
using the exiting view, let clear the focus of before we remove it from
the fragment.
RelNote: "The keyboard will now close automatically when going from
a fragment with an open keyboard to a fragment with a recycler view."
Test: tested in sample app from bug
Bug: 196852211
Change-Id: I8b842dd9a421cfbc9189014b802f5e4b6b9c2a47
M fragment/fragment/src/main/java/androidx/fragment/app/SpecialEffectsController.java
https://android-review.googlesource.com/1847143
Branch: androidx-main
commit b9b1326edfe38588a9882e1ee624798966c5686a
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed Oct 06 16:49:53 2021
Clear focus on Fragments animating out
Since moving to the new state manager, fragment now explicitly handle
focus where in the old world they could ignore it altogether. This
change has the side effect that other things affected by focus (i.e.
soft keyboard input) are affect as well. In particular when we
requestFocus we update the input request, but since we never clear it
users have to manually remove the input.
When we are animating a fragment view out, since we will no longer be
using the exiting view, let clear the focus of before we remove it from
the fragment.
RelNote: "The keyboard will now close automatically when going from
a fragment with an open keyboard to a fragment with a recycler view."
Test: tested in sample app from bug
Bug: 196852211
Change-Id: I8b842dd9a421cfbc9189014b802f5e4b6b9c2a47
M fragment/fragment/src/main/java/androidx/fragment/app/SpecialEffectsController.java
an...@google.com <an...@google.com> #3
This has been fixed internally and will be available in the Fragment 1.4.0-beta01
release.
an...@google.com <an...@google.com> #4
The issue still persist in API version 27 and below in Fragment 1.4.0
[Deleted User] <[Deleted User]> #5
We're still seeing this faulty behaviour in version 1.0.1, is this issue truly fixed?
[Deleted User] <[Deleted User]> #6
I don't think this issue is fixed, I am still facing it.
ib...@gmail.com <ib...@gmail.com> #7
Issue is not fixed even on version 1.1.0
sa...@gmail.com <sa...@gmail.com> #8
The issue still happens when we use a password/pin in version 1.2.0-alpha05.
sa...@gmail.com <sa...@gmail.com> #9
The issue still happens when we use a password/pin in version 1.2.0-alpha05.
Condition: Turn ON the "Don't Keep Activities" option in the "Developer Options."
Condition: Turn ON the "Don't Keep Activities" option in the "Developer Options."
Description
When I tap use password I get an error from the callback "Unknown error 10" and then when I enter my PIN code or fingerprint callback is not called.
BUILD INFO
- Device type: Samsung A50
- OS version: Android 9
- Biometric library version: "androidx.biometric:biometric:1.0.0-rc02"
STEPS TO REPRODUCE
1. Face recognition enabled, face registered and set as preferred biometric
2. Fingerprint registered and enabled (required to show face recognition prompt, see
3. PIN required to unlock device
4. setDeviceCredentialAllowed(true)
5. Face recognition prompt showing, tap use password
6. Enter PIN code or fingerprint (black screen in video)
EXPECTED RESULTS
Toast showing "Authentication successful" from callback method onAuthenticationSucceeded
OBSERVED RESULTS
Toast showing error at step 5 and callback not called when entering pin code or fingerprint
NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE 100%
Thank you