[GH-ISSUE #3808] Creating passkey for WhatsApp, it failed successfully #88413

Closed
opened 2026-05-26 21:43:42 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @JasonHK on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/3808

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. Create a passkey inside WhatsApp

Expected Result

A passkey was created, WhatsApp congrats you the passkey was created.

Actual Result

A passkey was created, but WhatsApp doesn’t know the passkey was created, hence “failed successfully”.

Screenshots or Videos

https://github.com/user-attachments/assets/8751ef46-4d24-41bc-959c-df79cd6f8af5

Additional Context

No response

Build Version

2024.8.0 (18985)

Environment Details

  • Device: Samsung Galaxy S21 5G
  • OS Version: Android 14, One UI 6.1

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 @JasonHK on GitHub (Aug 22, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/3808 ### 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. Create a passkey inside WhatsApp ### Expected Result A passkey was created, WhatsApp congrats you the passkey was created. ### Actual Result A passkey was created, but WhatsApp doesn’t know the passkey was created, hence “failed successfully”. ### Screenshots or Videos https://github.com/user-attachments/assets/8751ef46-4d24-41bc-959c-df79cd6f8af5 ### Additional Context _No response_ ### Build Version 2024.8.0 (18985) ### Environment Details - Device: Samsung Galaxy S21 5G - OS Version: Android 14, One UI 6.1 ### 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 2026-05-26 21:43:42 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Aug 22, 2024):

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

<!-- gh-comment-id:2305373831 --> @bitwarden-bot commented on GitHub (Aug 22, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-11268
Author
Owner

@daniellbw commented on GitHub (Aug 26, 2024):

Hi there,

Your issue appears to be describing the intended behavior of the software.
For Android "while passkeys for web browsers are supported, support for is apps coming soon in a future beta build". : https://bitwarden.com/help/storing-passkeys/#tab-android-(beta)-3XutklkReT3Gw0l1qHhBem

We use GitHub issues as a place to track bugs and other development related issues.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:2309464219 --> @daniellbw commented on GitHub (Aug 26, 2024): Hi there, Your issue appears to be describing the intended behavior of the software. For Android "while passkeys for web browsers are supported, support for is apps coming soon in a future beta build". : https://bitwarden.com/help/storing-passkeys/#tab-android-(beta)-3XutklkReT3Gw0l1qHhBem We use GitHub issues as a place to track bugs and other development related issues. This issue will now be closed. Thanks!
Author
Owner

@MrRoiz commented on GitHub (Feb 19, 2025):

Any update on this? I got the same error on current android latest version

<!-- gh-comment-id:2669966735 --> @MrRoiz commented on GitHub (Feb 19, 2025): Any update on this? I got the same error on current android latest version
Author
Owner

@SaintPatrck commented on GitHub (Feb 20, 2025):

Hi all,

Bitwarden successfully processes and responds to the passkey request without issue. We believe this is an bug in WhatsApp's implementation. More details can be found in comment https://github.com/bitwarden/android/issues/4582#issuecomment-2631639765.

Since passkey creation does work during initial sign-in, but not when you are currently signed in, I suggest reporting this behavior to WhatsApp for further investigation.

<!-- gh-comment-id:2671679339 --> @SaintPatrck commented on GitHub (Feb 20, 2025): Hi all, Bitwarden successfully processes and responds to the passkey request without issue. We believe this is an bug in WhatsApp's implementation. More details can be found in comment https://github.com/bitwarden/android/issues/4582#issuecomment-2631639765. Since passkey creation does work during initial sign-in, but not when you are currently signed in, I suggest reporting this behavior to WhatsApp for further investigation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#88413