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

[PR #2774] [PM-3811] Passkeys unification #3800

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

Original Pull Request: https://github.com/bitwarden/android/pull/2774

State: closed
Merged: Yes

Type of change

  • Bug fix
  • New feature development
  • Tech debt (refactoring, code cleanup, dependency upgrades, etc)
  • Build/deploy pipeline (DevOps)
  • Other

Objective

Unify both passkeys to be displayed inside a Login cipher, also change the Login Fido2Key to be an array where the passkeys will be stored.

Code changes

  • Cipher/Data/Request/Response/View: Removed Fido2Key and added some helpers given that the passkeys will be stored inside the Login item.
  • Login/Data/Api: Changed Fido2Key to be an array and added some helpers inside to handle it easier. Also added MainFido2Key given that for the moment only one Fido2Key will exist in the array.
  • CipherAddEditPage/ViewModel / CipherDetailsPage/ViewModel: Unified to only display CreationDate as Passkey data.
  • CipherDetailsPageViewModel: Updated can clone logic.
  • Others: Updated logic for new array approach.

Screenshots

Cipher details Light

Cipher details Light

Cipher details Dark

Cipher details Dark

Cipher edition Light

Cipher edition Light

Cipher edition Dark

Cipher edition Dark

Before you submit

  • Please check for formatting errors (dotnet format --verify-no-changes) (required)
  • Please add unit tests where it makes sense to do so (encouraged but not required)
  • If this change requires a documentation update - notify the documentation team
  • If this change has particular deployment requirements - notify the DevOps team
**Original Pull Request:** https://github.com/bitwarden/android/pull/2774 **State:** closed **Merged:** Yes --- ## Type of change - [ ] Bug fix - [X] New feature development - [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc) - [ ] Build/deploy pipeline (DevOps) - [ ] Other ## Objective <!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding--> Unify both passkeys to be displayed inside a Login cipher, also change the Login `Fido2Key` to be an array where the passkeys will be stored. ## Code changes <!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes--> <!--Also refer to any related changes or PRs in other repositories--> * **Cipher/Data/Request/Response/View:** Removed `Fido2Key` and added some helpers given that the passkeys will be stored inside the `Login` item. * **Login/Data/Api:** Changed `Fido2Key` to be an array and added some helpers inside to handle it easier. Also added `MainFido2Key` given that for the moment only one `Fido2Key` will exist in the array. * **CipherAddEditPage/ViewModel / CipherDetailsPage/ViewModel:** Unified to only display `CreationDate` as `Passkey` data. * **CipherDetailsPageViewModel:** Updated can clone logic. * **Others:** Updated logic for new array approach. ## Screenshots <!--Required for any UI changes. Delete if not applicable--> ### Cipher details Light <img width="314" alt="Cipher details Light" src="https://github.com/bitwarden/mobile/assets/15682323/6492bd57-0958-4cb9-9282-a5b806e0bcdb"> ### Cipher details Dark <img width="314" alt="Cipher details Dark" src="https://github.com/bitwarden/mobile/assets/15682323/9930a661-e971-4be3-89fe-db63d109016f"> ### Cipher edition Light <img width="314" alt="Cipher edition Light" src="https://github.com/bitwarden/mobile/assets/15682323/2ee389ce-27d6-4b0d-9929-aa21b5aae91b"> ### Cipher edition Dark <img width="314" alt="Cipher edition Dark" src="https://github.com/bitwarden/mobile/assets/15682323/cb3a3d8b-fd06-47a8-949b-58305364f2dc"> ## Before you submit - Please check for formatting errors (`dotnet format --verify-no-changes`) (required) - Please add **unit tests** where it makes sense to do so (encouraged but not required) - If this change requires a **documentation update** - notify the documentation team - If this change has particular **deployment requirements** - notify the DevOps team
GiteaMirror added the pull-request label 2025-11-26 23:37:20 -06:00
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 pull-request
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#3800
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?