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

Passkey login failing on android #2079

New Issue
Closed
opened 2025-11-26 23:07:20 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 23:07:20 -06:00
Owner
Copy Link

Originally created by @DariB123 on GitHub (Nov 23, 2024).

Steps To Reproduce

  1. Click on 'sign in with passkey'
    1
  2. Unlock bitwarden vault
    2
  3. Click on 'Continue'
    3

Expected Result

Login with passkey should succeed.

Actual Result

Passkey login fails with prompt "Error reading passkey" and "There was a problem reading your passkey for. Try again later."

Screenshots or Videos

No response

Additional Context

I've also tried with this other services I have passkey login for and have experienced the same behavior.

Build Version

2024.10.0 (11270)

What server are you connecting to?

Self-host

Self-host Server Version

No response

Environment Details

  • Browser: ms-edge (also tried on google-chrome)

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 @DariB123 on GitHub (Nov 23, 2024). ### Steps To Reproduce 1. Click on 'sign in with passkey' ![1](https://github.com/user-attachments/assets/f9e07355-2ee7-4711-b74e-91b89bfdc9b3) 2. Unlock bitwarden vault ![2](https://github.com/user-attachments/assets/abf6b4b3-1e75-40b8-bf9d-7e0bd510f319) 3. Click on 'Continue' ![3](https://github.com/user-attachments/assets/234713b0-7fca-4d10-87ce-c0288446d226) ### Expected Result Login with passkey should succeed. ### Actual Result Passkey login fails with prompt "Error reading passkey" and "There was a problem reading your passkey for. Try again later." ### Screenshots or Videos _No response_ ### Additional Context I've also tried with this other services I have passkey login for and have experienced the same behavior. ### Build Version 2024.10.0 (11270) ### What server are you connecting to? Self-host ### Self-host Server Version _No response_ ### Environment Details - Browser: ms-edge (also tried on google-chrome) ### 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:07:20 -06:00
GiteaMirror commented 2025-11-26 23:07:21 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Nov 23, 2024):

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

@bitwarden-bot commented on GitHub (Nov 23, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-15221
GiteaMirror commented 2025-11-26 23:07:21 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Nov 25, 2024):

Hello there,

Can you please share your Android version and which version of Bitwarden you are self-hosting?

@Krychaz commented on GitHub (Nov 25, 2024): Hello there, Can you please share your Android version and which version of Bitwarden you are self-hosting?
GiteaMirror commented 2025-11-26 23:07:21 -06:00
Author
Owner
Copy Link

@DariB123 commented on GitHub (Nov 25, 2024):

I'm on Android 15, build number AP3A.241105.008.

I'm self hosting the latest version vaultwarden at the moment, I'd be curious to see if anybody can replicate this issue on regular bitwarden. I'm not really convinced it'll make a difference because logging in using a passkey via the browser extension works fine.

@DariB123 commented on GitHub (Nov 25, 2024): I'm on Android 15, build number AP3A.241105.008. I'm self hosting the latest version vaultwarden at the moment, I'd be curious to see if anybody can replicate this issue on regular bitwarden. I'm not really convinced it'll make a difference because logging in using a passkey via the browser extension works fine.
GiteaMirror commented 2025-11-26 23:07:21 -06:00
Author
Owner
Copy Link

@Krychaz commented on GitHub (Nov 26, 2024):

Vaultwarden has support for the new native mobile apps apps in version 1.31.0 and above and you may need to upgrade your server. Another way to confirm that you need to upgrade your server is that you should be able to log into other clients (i.e. the browser extension or the web app) with the old Vaultwarden version.

It is important to note that vaultwarden is not associated with Bitwarden.

Vaultwarden is a re-writing of the Bitwarden server code in Rust, that is not contributed to or supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to vaultwarden, and the Bitwarden support team is not able to respond to questions regarding vaultwarden.

@Krychaz commented on GitHub (Nov 26, 2024): Vaultwarden has support for the new native mobile apps apps in version 1.31.0 and above and you may need to upgrade your server. Another way to confirm that you need to upgrade your server is that you should be able to log into other clients (i.e. the browser extension or the web app) with the old Vaultwarden version. It is important to note that vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust, that is not contributed to or supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to vaultwarden, and the Bitwarden support team is not able to respond to questions regarding vaultwarden.
GiteaMirror commented 2025-11-26 23:07:21 -06:00
Author
Owner
Copy Link

@singh9596 commented on GitHub (Dec 16, 2024):

Yes, passkey doesn't work to login as well. For now switch back to 2024.11.3.

@singh9596 commented on GitHub (Dec 16, 2024): Yes, passkey doesn't work to login as well. For now switch back to 2024.11.3.
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#2079
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?