github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 14:16:23 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Update fido2_privileged_google.json #2030

New Issue
Closed
opened 2025-11-26 23:05:44 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-26 23:05:44 -06:00
Owner
Copy Link

Originally created by @ZingLix on GitHub (Oct 18, 2024).

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Attempt to log in with a passkey on another device, and choose the option to authenticate using a different device. A QR code will be displayed.
  2. Use a phone with Bitwarden installed to scan the QR code.
  3. The system will then prompt Bitwarden to authenticate the passkey.

Expected Result

Bitwarden should complete the authentication process.

Actual Result

Bitwarden encountered the error: 'Passkey operation failed because the browser is not privileged.'

Screenshots or Videos

No response

Additional Context

I noticed that com.fido.fido2client is included in the allowlist provided by Google, but it is missing from fido2_privileged_google.json. Should we consider updating the allowlist?

Build Version

2024.9.0 (19209)

Environment Details

Android 15

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @ZingLix on GitHub (Oct 18, 2024). ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Attempt to log in with a passkey on another device, and choose the option to authenticate using a different device. A QR code will be displayed. 2. Use a phone with Bitwarden installed to scan the QR code. 3. The system will then prompt Bitwarden to authenticate the passkey. ### Expected Result Bitwarden should complete the authentication process. ### Actual Result Bitwarden encountered the error: 'Passkey operation failed because the browser is not privileged.' ### Screenshots or Videos _No response_ ### Additional Context I noticed that `com.fido.fido2client` is included in the allowlist provided by [Google](https://www.gstatic.com/gpm-passkeys-privileged-apps/apps.json), but it is missing from `fido2_privileged_google.json`. Should we consider updating the allowlist? ### Build Version 2024.9.0 (19209) ### Environment Details Android 15 ### Issue Tracking Info - [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug label 2025-11-26 23:05:44 -06:00
GiteaMirror commented 2025-11-26 23:05:45 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Oct 18, 2024):

Thank you for your report! We've added this to our internal board for review.
ID: PM-13825

@bitwarden-bot commented on GitHub (Oct 18, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-13825
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#2030
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?