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

LineageOS 21: Bitwarden cannot be used for passkey authentication on mobile #1907

New Issue
Closed
opened 2025-11-26 23:01:14 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-26 23:01:14 -06:00
Owner
Copy Link

Originally created by @somova on GitHub (Jun 15, 2024).

Steps To Reproduce

  1. Ensure Bitwarden mobile is set as provider for "Passwords, Passkeys and Data Services"
  2. Open mobile Browser
  3. Open webpage "https://webauthn.io/"
  4. Try to register a passkey or authenticate with a passkey

Expected Result

Android should offer to select the favorite passkey provider to use with the webpage

Actual Result

Google only offers to store a new or use an already stored passkey in the Google Account or to select another device. The list of other devices only contains NFC, USB or other smartphone.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

LineageOS 21 (Build: 20240610; Android 14)

Device

Oneplus 9 Pro (LE2123)

Build Version

2024.5.1 (10574)

Beta

  • Using a pre-release version of the application.
Originally created by @somova on GitHub (Jun 15, 2024). ### Steps To Reproduce 1. Ensure Bitwarden mobile is set as provider for "Passwords, Passkeys and Data Services" 2. Open mobile Browser 3. Open webpage "https://webauthn.io/" 4. Try to register a passkey or authenticate with a passkey ### Expected Result Android should offer to select the favorite passkey provider to use with the webpage ### Actual Result Google only offers to store a new or use an already stored passkey in the Google Account or to select another device. The list of other devices only contains NFC, USB or other smartphone. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Android ### Operating System Version LineageOS 21 (Build: 20240610; Android 14) ### Device Oneplus 9 Pro (LE2123) ### Build Version 2024.5.1 (10574) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 23:01:14 -06:00
GiteaMirror commented 2025-11-26 23:01:15 -06:00
Author
Owner
Copy Link

@SergeantConfused commented on GitHub (Jun 15, 2024):

Hi @somova,

Thank you for this report. Did you test this in Chrome after performing the steps that are outlined in the documentation?

Thank you in advance,

@SergeantConfused commented on GitHub (Jun 15, 2024): Hi @somova, Thank you for this report. Did you test this in Chrome after performing the steps that are [outlined in the documentation](https://bitwarden.com/help/auto-fill-android/#setup-bitwarden-for-use-with-passkeys)? Thank you in advance,
GiteaMirror commented 2025-11-26 23:01:16 -06:00
Author
Owner
Copy Link

@somova commented on GitHub (Jun 16, 2024):

Sorry, I forgot to mention the tested apps:

  • Vivaldi mobile browser (v.6.7.3335.149)
  • Firefox mobile browser (v.127.0)
  • Chrome mobile browser (v.126.0.6478.71)

Additionally, I followed the documentation and enabled flag "M124", but no avail.

Addition:
At first I did not find the second option (Enabled for 3rd party passkey providers under Android Credential Management for passkeys). After a closer look I found and enabled it. Now, the Chrome browser shows a bitwarden prompt when authenticating at "webauthn.io", but throws the following error message:

Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut

Since my LineageOS smartphone is rooted. Are there any log files I could inspect?

@somova commented on GitHub (Jun 16, 2024): Sorry, I forgot to mention the tested apps: - Vivaldi mobile browser (v.6.7.3335.149) - Firefox mobile browser (v.127.0) - Chrome mobile browser (v.126.0.6478.71) Additionally, I followed the [documentation](https://bitwarden.com/help/auto-fill-android/#setup-bitwarden-for-use-with-passkeys) and enabled flag "M124", but no avail. _Addition:_ At first I did not find the second option (Enabled for 3rd party passkey providers under Android Credential Management for passkeys). After a closer look I found and enabled it. Now, the Chrome browser shows a bitwarden prompt when authenticating at "webauthn.io", but throws the following error message: `Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut` Since my LineageOS smartphone is rooted. Are there any log files I could inspect?
GiteaMirror commented 2025-11-26 23:01:16 -06:00
Author
Owner
Copy Link

@micahblut commented on GitHub (Jun 17, 2024):

@somova Do you know if LineageOS supports Google Play Services?

@micahblut commented on GitHub (Jun 17, 2024): @somova Do you know if LineageOS supports Google Play Services?
GiteaMirror commented 2025-11-26 23:01:16 -06:00
Author
Owner
Copy Link

@msiqx9 commented on GitHub (Jun 18, 2024):

@somova Do you know if LineageOS supports Google Play Services?

Yes, all my OnePlus phones with LineageOS 21 have Google Play Services installed.

@msiqx9 commented on GitHub (Jun 18, 2024): > @somova Do you know if LineageOS supports Google Play Services? Yes, all my OnePlus phones with LineageOS 21 have Google Play Services installed.
GiteaMirror commented 2025-11-26 23:01:16 -06:00
Author
Owner
Copy Link

@somova commented on GitHub (Jun 18, 2024):

@somova Do you know if LineageOS supports Google Play Services?

Yes, LineageOS supports Google Play Services. During initial installation phase of LineageOS the user can decide to add the Google addon package. On my smartphone Google Services including Google Play are available

@somova commented on GitHub (Jun 18, 2024): > @somova Do you know if LineageOS supports Google Play Services? Yes, LineageOS supports Google Play Services. During initial installation phase of LineageOS the user can decide to add the Google addon package. On my smartphone Google Services including Google Play are available
GiteaMirror commented 2025-11-26 23:01:16 -06:00
Author
Owner
Copy Link

@somova commented on GitHub (Jun 18, 2024):

Now authentication succeeds with the Chrome browser. The error message

Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut

disappers if the session timeout in the bitwarden mobile app is set to a value other than "immediately". Registering a passkey is still not offered.

@somova commented on GitHub (Jun 18, 2024): Now authentication succeeds with the Chrome browser. The error message > Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut disappers if the session timeout in the bitwarden mobile app is set to a value other than "immediately". Registering a passkey is still not offered.
GiteaMirror commented 2025-11-26 23:01:17 -06:00
Author
Owner
Copy Link

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

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

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/3310
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#1907
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?