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

[PR #5678] [MERGED] [PM-24568] Add accountKeys to SyncResponseJson.Profile #5962

New Issue
Closed
opened 2025-11-27 00:17:47 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-27 00:17:47 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/5678
Author: @SaintPatrck
Created: 8/11/2025
Status: ✅ Merged
Merged: 8/11/2025
Merged by: @SaintPatrck

Base: main ← Head: PM-24568/update-sync-response-model

📝 Commits (1)

  • e01cb3b [PM-24568] Add accountKeys to SyncResponseJson.Profile

📊 Changes

3 files changed (+150 additions, -0 deletions)

View changed files

📝 network/src/main/kotlin/com/bitwarden/network/model/SyncResponseJson.kt (+77 -0)
📝 network/src/test/kotlin/com/bitwarden/network/service/SyncServiceTest.kt (+17 -0)
📝 network/src/testFixtures/kotlin/com/bitwarden/network/model/SyncResponseProfileUtil.kt (+56 -0)

📄 Description

🎟️ Tracking

PM-24568

📔 Objective

Introduce the accountKeys field to the SyncResponseJson.Profile data class. This new field will hold the user's signature key pair, public key encryption key pair, and security state.

The privateKey field has been deprecated in favor of accountKeys.

Additionally, new test fixture utilities (createMockPrivateKeys, createMockSecurityState, createMockPublicKeyEncryptionKeyPair, createMockSignatureKeyPair) have been added to facilitate testing of this new structure. The existing SyncServiceTest has been updated to include accountKeys in its mock response.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/5678 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 8/11/2025 **Status:** ✅ Merged **Merged:** 8/11/2025 **Merged by:** [@SaintPatrck](https://github.com/SaintPatrck) **Base:** `main` ← **Head:** `PM-24568/update-sync-response-model` --- ### 📝 Commits (1) - [`e01cb3b`](https://github.com/bitwarden/android/commit/e01cb3bda9194cf5c5cb8ba83c288499686f4777) [PM-24568] Add `accountKeys` to `SyncResponseJson.Profile` ### 📊 Changes **3 files changed** (+150 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `network/src/main/kotlin/com/bitwarden/network/model/SyncResponseJson.kt` (+77 -0) 📝 `network/src/test/kotlin/com/bitwarden/network/service/SyncServiceTest.kt` (+17 -0) 📝 `network/src/testFixtures/kotlin/com/bitwarden/network/model/SyncResponseProfileUtil.kt` (+56 -0) </details> ### 📄 Description ## 🎟️ Tracking PM-24568 ## 📔 Objective Introduce the `accountKeys` field to the `SyncResponseJson.Profile` data class. This new field will hold the user's signature key pair, public key encryption key pair, and security state. The `privateKey` field has been deprecated in favor of `accountKeys`. Additionally, new test fixture utilities (`createMockPrivateKeys`, `createMockSecurityState`, `createMockPublicKeyEncryptionKeyPair`, `createMockSignatureKeyPair`) have been added to facilitate testing of this new structure. The existing `SyncServiceTest` has been updated to include `accountKeys` in its mock response. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Protected functional changes with optionality (feature flags) - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-27 00:17:47 -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#5962
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?