Assigned
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.
ni...@gmail.com <ni...@gmail.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?
ja...@gmail.com <ja...@gmail.com> #4
I see this on my android 14 emulator, but am pretty sure that I also saw it before on earlier android versions as well as on my pixel 8 with android 14.
sg...@google.com <sg...@google.com> #5
Thank you for reporting this. This is an known issue, we're working on a fix. Will update when it is ready.
jl...@figuremarkets.com <jl...@figuremarkets.com> #6
I'm also noticing this same issue on the latest stable version 1.2.2
Description
Component used:
Credentials
Version used:
1.3.0-alpha01 and prior versions as well
Devices/Android versions reproduced on:
Pixel 8
Example project:
Description:
When creating a new passkey on a device with multiple accounts, the account to link the passkey to by default seems to be chosen randomly.
Steps to reproduce:
Result:
A seemingly random, different account is chosen on every attempt. The same happens with apps installed from the play store
Expected:
The same account is chosen every time. That could be the account that was used to install the app or the default play store account.
Side note:
The chosen account is only mentioned very small at the bottom of the dialog and can easily be missed making it unclear to the user for what account they just created a passkey. I think the account should be highlighted more.
Example screenshots from my own testing using the steps outlined above:
See attached screenshots passkey1 and passkey2