[PM-39447] [Shared Unlock] Shared unlock stuck on lock component#21446
Conversation
Add externalUnlock$ observable to shared unlock leader/follower services, fired by JsSharedUnlockDriver when a user key is applied externally. Wire it into all platform LockComponentService implementations so the lock component navigates away automatically on external unlock.
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed the shared-unlock lock-screen fix that introduces an Code Review DetailsNo outstanding findings. Previously flagged test-compilation breakages (lock.component.spec, desktop-lock-component.service.spec, web-lock-component.service.spec) were resolved in this PR's follow-up commit. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #21446 +/- ##
==========================================
- Coverage 49.57% 49.56% -0.01%
==========================================
Files 4108 4109 +1
Lines 129059 129094 +35
Branches 19721 19722 +1
==========================================
+ Hits 63977 63989 +12
- Misses 60353 60377 +24
+ Partials 4729 4728 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Changes in this PR impact the Autofill experience of the browser clientBIT has tested the core experience with these changes and all feature flags disabled. ✅ Fortunately, these BIT tests have passed! 🎉 |
Changes in this PR impact the Autofill experience of the browser clientBIT has tested the core experience with these changes and the feature flag configuration used by ✅ Fortunately, these BIT tests have passed! 🎉 |



🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-39447
📔 Objective
Bug: When two clients sharing unlock are on the lock screen actively, then one unlocks, while the other also unlocks, it remains on the lock component and never navigates away.
This fixes it by adding an external unlock event which the lock components use to navigate away.
📸 Screenshots
N/A