Page MenuHomePhabricator

[lib] broadcast updates to all peers after Secondary Device registration success
ClosedPublic

Authored by kamil on Jun 13 2024, 9:37 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 2:38 PM
Unknown Object (File)
Sat, Oct 26, 4:36 PM
Unknown Object (File)
Oct 24 2024, 4:05 AM
Unknown Object (File)
Oct 12 2024, 1:26 PM
Unknown Object (File)
Oct 12 2024, 1:26 PM
Unknown Object (File)
Oct 12 2024, 1:26 PM
Unknown Object (File)
Oct 12 2024, 1:26 PM
Unknown Object (File)
Oct 12 2024, 1:26 PM
Subscribers

Details

Summary

After discussion with @bartek we concluded that after receiving SECONDARY_DEVICE_REGISTRATION_SUCCESS we should:

  1. Broadcast update to all peers
  2. Update our own store (we have to call getAndUpdateDeviceListsForUsers to get platform details of new device).

Depends on D12374

Test Plan

Going to test along with fixes to ENG-8385.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Jun 13 2024, 9:51 AM
This revision is now accepted and ready to land.Jun 13 2024, 9:54 PM