github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-08-18 10:17:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #6610] [PM-33064] Trouble creating WhatsApp passkey #102539

New Issue
Closed
opened 2026-06-03 02:31:15 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-03 02:31:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @AdriandeLima on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6610

Steps To Reproduce

I already had my WhatsApp info saved to bitwarden (passcode etc.) and it had the WhatsApp website saved to the entry.

When I went to create a passkey in WhatsApp, bitwarden said there was no matching entries and I'm prompted to create a new entry (understandable as the WhatsApp entry isn't linked to the app, it's linked to the website.)

The problem (or bug) is that when I search for the existing WhatsApp entry (to avoid duplicate entries) to save the passkey, I only get the option to edit the existing entry, there's no option to save the passkey to it.

Expected Result

I should be allowed to save a passkey to an existing entry.

Actual Result

I am unable to save the passkey to an existing entry without editing the entry and adding the URL android//com.whatsapp

Screenshots or Videos

No response

Additional Context

I don't know what server I'm connected to, but it's a standard bitwarden setup.

Build Version

Version 2026.2.0 com.x8bit.bitwarden

What server are you connecting to?

N/A

Self-host Server Version

No response

Environment Details

No response

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 @AdriandeLima on GitHub (Mar 2, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6610 ### Steps To Reproduce I already had my WhatsApp info saved to bitwarden (passcode etc.) and it had the WhatsApp website saved to the entry. When I went to create a passkey in WhatsApp, bitwarden said there was no matching entries and I'm prompted to create a new entry (understandable as the WhatsApp entry isn't linked to the app, it's linked to the website.) The problem (or bug) is that when I search for the existing WhatsApp entry (to avoid duplicate entries) to save the passkey, I only get the option to edit the existing entry, there's no option to save the passkey to it. ### Expected Result I should be allowed to save a passkey to an existing entry. ### Actual Result I am unable to save the passkey to an existing entry without editing the entry and adding the URL android//com.whatsapp ### Screenshots or Videos _No response_ ### Additional Context I don't know what server I'm connected to, but it's a standard bitwarden setup. ### Build Version Version 2026.2.0 com.x8bit.bitwarden ### What server are you connecting to? N/A ### Self-host Server Version _No response_ ### Environment Details _No response_ ### 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 bugapp:password-manager labels 2026-06-03 02:31:16 -05:00
GiteaMirror commented 2026-06-03 02:31:18 -05:00
Author
Owner
Copy Link
Copy Source

@bitwarden-bot commented on GitHub (Mar 2, 2026):

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

<!-- gh-comment-id:3987482358 --> @bitwarden-bot commented on GitHub (Mar 2, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-33064](https://bitwarden.atlassian.net/browse/PM-33064) [PM-33064]: https://bitwarden.atlassian.net/browse/PM-33064?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-06-03 02:31:18 -05:00
Author
Owner
Copy Link
Copy Source

@rmcdowell-bitwarden commented on GitHub (Mar 2, 2026):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/5329.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:3987711132 --> @rmcdowell-bitwarden commented on GitHub (Mar 2, 2026): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/5329. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thanks!
GiteaMirror commented 2026-06-03 02:31:18 -05:00
Author
Owner
Copy Link
Copy Source

@AdriandeLima commented on GitHub (Mar 3, 2026):

Hi, upon going through the process again to get screenshots, I've discovered it's not a bug, just an unintuitive workflow. You have to edit your existing entry, and then click save, even though you didn't change anything. This creates the passkey inside the entry. I had assumed editing the entry was just for adding information manually, it might be worth looking into the UX of this workflow.

<!-- gh-comment-id:3991220949 --> @AdriandeLima commented on GitHub (Mar 3, 2026): Hi, upon going through the process again to get screenshots, I've discovered it's not a bug, just an unintuitive workflow. You have to edit your existing entry, and then click save, even though you didn't change anything. This creates the passkey inside the entry. I had assumed editing the entry was just for adding information manually, it might be worth looking into the UX of this workflow.
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 labels app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#102539