Assigned
Status Update
No update yet.
Comments
bl...@google.com
Automated by Blunderbuss job android-credential-manager-autoassigner for config android_credman_config for component 1301097.
re...@google.com
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?
hi...@cplcloud.com
Hi, Please find the video attached for further clarification .
The timeout for the FIDO2 registration Request has been set to 30 seconds.
There are two attachments and you can see one of the attachment completed the registration request in 7 seconds and get the registration response for the JSON and another one done in 16 seconds and gets timeout error but the actual timeout is 30 seconds. Same observation for the 60 seconds and 120 seconds too .
The timeout for the FIDO2 registration Request has been set to 30 seconds.
There are two attachments and you can see one of the attachment completed the registration request in 7 seconds and get the registration response for the JSON and another one done in 16 seconds and gets timeout error but the actual timeout is 30 seconds. Same observation for the 60 seconds and 120 seconds too .
re...@google.com
sg...@google.com
The videos attached in $4 doesn't work. It just shows a blank screen.
Also could you please grab bugreport which could help look into more details.
hi...@cplcloud.com
Hi Jerry,
Please refer to the videos attached again. The video has a view which shows the exception thrown by the credential manager API when the timeout happens .
The timeout for the FIDO2 registration Request has been set to 30 seconds.
There are two attachments and you can see one of the attachment completed the registration request in 7 seconds and get the registration response for the JSON and another one done in 16 seconds and gets timeout error but the actual timeout is 30 seconds. Same observation for the 60 seconds and 120 seconds too .
Please refer to the videos attached again. The video has a view which shows the exception thrown by the credential manager API when the timeout happens .
The timeout for the FIDO2 registration Request has been set to 30 seconds.
There are two attachments and you can see one of the attachment completed the registration request in 7 seconds and get the registration response for the JSON and another one done in 16 seconds and gets timeout error but the actual timeout is 30 seconds. Same observation for the 60 seconds and 120 seconds too .
Description
Version used: 1.2.2, 1.3.0
Devices/Android versions reproduced on: Pixel 7, Android 15
Issue:
There is a mismatch between the requested and actual timeout values when using the Passkeys FIDO2Request timeout on Android 15.
Steps to reproduce:
Use a Pixel 7 device running Android 15.
Set a timeout for the Passkeys FIDO2Request (e.g., 60 seconds).
Observe the actual timeout behavior.
Expected behavior:
The Passkeys Authenticator should respect the requested timeout duration.
Actual behavior:
The actual timeout is always half of the requested value. For example:
Requested timeout: 60 seconds
Actual timeout: 30 seconds
Observed behavior across different API versions and devices:
Credentials API version 1.2.2:
Device: Pixel 7, Android 15
Timeout Requested Actual Timeout
15 seconds 7.5 seconds
30 seconds 15 seconds
60 seconds 30 seconds
120 seconds 60 seconds
Credentials API version 1.3.0:
Device: Pixel 7, Android 15
Timeout Requested Actual Timeout
15 seconds 7.5 seconds
30 seconds 15 seconds
60 seconds 30 seconds
120 seconds 60 seconds
Note:
This issue does not occur on Android 12 with a Pixel 3 device with Credentials API 1.2.2. and 1.3.0