github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-06 07:48:22 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #3228] Android beta - passkey autofill not working when session timeout set to 'immediately' #27757

New Issue
Closed
opened 2026-04-18 11:18:25 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 11:18:25 -05:00
Owner
Copy Link

Originally created by @MrSourceUnknown on GitHub (May 7, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3228

Steps To Reproduce

Not working:

  • Go to Settings → account security → session timeout and set it to 'Immediately'
  • try to use a passkey anywhere to logon
  • after unlocking the vault and selecting the correct passkey it throws an error saying 'something went wong'

Working:

  • Go to Settings → account security → session timeout and choose any option except 'immediately'
  • try to use a passkey anywhere to logon
  • after unlocking the vault and selecting the correct passkey it is accepted

Expected Result

I would expect the passkey autofill logic to work even when session timeout is set to 'immediately' as that is how it works for password autofill as well.

Actual Result

Instead when using autofill the session timeout seems to trigger partway through the selection process.

Screenshots or Videos

No response

Additional Context

Browser used: Chrome version 124.0.6367.113, with 3rd party passkey flag enabled.
Site tested: google account logon using passkey option

Operating System

Android

Operating System Version

14

Device

Pixel 6 Pro

Build Version

2024.4.1 (10283)

Beta

  • Using a pre-release version of the application.
Originally created by @MrSourceUnknown on GitHub (May 7, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3228 ### Steps To Reproduce Not working: - Go to Settings → account security → session timeout and set it to 'Immediately' - try to use a passkey anywhere to logon - after unlocking the vault and selecting the correct passkey it throws an error saying 'something went wong' Working: - Go to Settings → account security → session timeout and choose any option _except_ 'immediately' - try to use a passkey anywhere to logon - after unlocking the vault and selecting the correct passkey it is accepted ### Expected Result I would expect the passkey autofill logic to work even when session timeout is set to 'immediately' as that is how it works for password autofill as well. ### Actual Result Instead when using autofill the session timeout seems to trigger partway through the selection process. ### Screenshots or Videos _No response_ ### Additional Context Browser used: Chrome version 124.0.6367.113, with 3rd party passkey flag enabled. Site tested: google account logon using passkey option ### Operating System Android ### Operating System Version 14 ### Device Pixel 6 Pro ### Build Version 2024.4.1 (10283) ### Beta - [X] Using a pre-release version of the application.
GiteaMirror added the bug label 2026-04-18 11:18:25 -05:00
GiteaMirror commented 2026-04-18 11:18:27 -05:00
Author
Owner
Copy Link

@micahblut commented on GitHub (May 9, 2024):

@MrSourceUnknown thank you for taking the time to test the beta and report this issue. We've replicated the issue and will work on a fix.

<!-- gh-comment-id:2102568833 --> @micahblut commented on GitHub (May 9, 2024): @MrSourceUnknown thank you for taking the time to test the beta and report this issue. We've replicated the issue and will work on a fix.
GiteaMirror commented 2026-04-18 11:18:28 -05:00
Author
Owner
Copy Link

@MrSourceUnknown commented on GitHub (May 12, 2024):

Thanks!

It's not a massive bother, but good that it was reproducible and will be looked into.

<!-- gh-comment-id:2106377476 --> @MrSourceUnknown commented on GitHub (May 12, 2024): Thanks! It's not a massive bother, but good that it was reproducible and will be looked into.
GiteaMirror commented 2026-04-18 11:18:28 -05:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/3228

<!-- gh-comment-id:2181381208 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/3228
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#27757
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?