In Progress
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Automated by Blunderbuss job android-credential-manager-autoassigner for config android_credman_config for component 1301097.
an...@rakuten.com <an...@rakuten.com> #3
The error you posted state "activity is cancelled by the user". This implies the request was cancelled somehow during the request.
Can you grab a bugreport and attach it to this bug?
de...@google.com <de...@google.com> #4
Hi, thanks for the report! What is the GMSCore version on the device? Can you check which providers are enabled in Android Settings, Passwords & Passkeys section.
sg...@google.com <sg...@google.com> #5
please provide information per
an...@rakuten.com <an...@rakuten.com> #6
Hi Derinel, Jerry.
Here are some screenshots, it seems we are unable to get both from the settings. The phone is owned by a member of our team China. I hope this helps.
Here are some screenshots, it seems we are unable to get both from the settings. The phone is owned by a member of our team China. I hope this helps.
an...@rakuten.com <an...@rakuten.com> #7
Hi Derinel, Jerinel
I have attached additional screenshots from the device, let me know if anything else needed to be provided.
Thanks!
I have attached additional screenshots from the device, let me know if anything else needed to be provided.
Thanks!
Description
Version used: Chrome 131.0.6778.135
Devices/Android versions reproduced on: Redmi Note 12 Turbo / Android 14 (UKQ1.230804.001)
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue: It is a bug we encountered while testing on
- A screenrecord or screenshots showing the issue (if UI related): attached the screenshot
The behaviour seems to be that the `navigation.credentials.create(...)` (clicking Register) suspends indefinitely. From one of the screenshots, we can see the log "Conditional UI request was aborted". Trying to invoke the `navigation.credentials.create()` again gives us the error "A request is already pending". A similar result is encountered when triggering `navigation.credentials.get(...)` (clicking Authenticate);