Page MenuHomePhabricator

[native] Notify primary device on registration finish
ClosedPublic

Authored by bartek on Mar 11 2024, 6:18 AM.
Tags
None
Referenced Files
F3113710: D11296.id37993.diff
Thu, Oct 31, 6:24 PM
Unknown Object (File)
Sun, Oct 27, 8:20 AM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Unknown Object (File)
Tue, Oct 22, 3:04 PM
Subscribers

Details

Summary

After successful registration (D11295), secondary device notifies primary device that it has performed device key upload. At this point, primary device can continue (next diffs)

Depends on D11295

Test Plan

An alert is displayed on primary device after successful device keys upload on secondary device

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek edited the test plan for this revision. (Show Details)
bartek published this revision for review.Mar 12 2024, 2:20 AM
native/qr-code/qr-code-screen.react.js
59

I would apply "De Morgan's Law" here

67

Is this console.log left over from debuggin?

Do we have some alternatives to detect that secondary device auth succeded other than isAuthorized from Tunnelbroker? Wondering if this is the best approach

native/profile/secondary-device-qr-code-scanner.react.js
103

I think you should use peerToPeerMessageValidator here

This revision is now accepted and ready to land.Mar 13 2024, 5:58 AM
native/qr-code/qr-code-screen.react.js
67

Yeah, leftover, thanks