No response from CredentialManager.getCredential(..)

[danchoo21]

Execution Environment:

OS: Android 14
Device: Samsung Galaxy S24
Issue:
After calling CredentialManager.getCredential(..), the BottomSheetDialog does not appear, and there is no response.

I encountered this issue.
When I tried to reproduce it, I observed the following behavior:
If the dialog fails to open properly for some reason, the suspend function locked and does not proceed. but not crash and not throw exception.

Test Environment:

Virtual Device: Pixel 8 Pro (API 34)
Reproduction Steps:

Touch the screen to close the BottomSheetDialog before it fully appears.
Observed Behavior:

After calling CredentialManager.getCredential(..), there is no response.

---

It occurs in the following API.

@RequiresApi(34)
suspend fun getCredential(
context: Context,
pendingGetCredentialHandle: PrepareGetCredentialResponse.PendingGetCredentialHandle,
) : GetCredentialResponse

suspend fun getCredential(
context: Context,
request: GetCredentialRequest,
): GetCredentialResponse

[niharika2810]

Thanks, would you mind creating a bug with all details required in that template if still the case? Sharing here : https://issuetracker.google.com/issues/new?component=1301097&template=1773864

[expcapitaldev]

hi guys, we have similar issue but only on
OS: Android 14
Device: Samsung Galaxy S24
and we can not reproduce on Pixel 6

[expcapitaldev]

need to check/create issue on issuetracker

[expcapitaldev]

https://issuetracker.google.com/issues/341690734

[fereshteh-jvz]

Is there any update? I have the same issue on Xiaomi devices on 10 and 12 android versions.. If the user clicks on the screen before the bottomsheet is opened, the ui freezes and bottomsheet takes a very long time to show up (sometimes it takes 4 minutes). This is very behavior and we have it on the production.

[cy245]

You can check the issuetracker link for more updates - there is a plan to fix this next year. Alternatively if this is a test device and you have a large number of passkeys/logins, deleting some should help fix this issue.