Page MenuHomePhabricator

[native] handle waiting for secondary device response
ClosedPublic

Authored by kamil on Thu, Dec 12, 11:49 AM.
Tags
None
Referenced Files
F3520797: D14153.id46553.diff
Mon, Dec 23, 1:23 AM
F3520608: D14153.id46390.diff
Mon, Dec 23, 12:47 AM
Unknown Object (File)
Sun, Dec 22, 2:59 AM
Unknown Object (File)
Sat, Dec 21, 12:35 AM
Unknown Object (File)
Thu, Dec 19, 9:56 PM
Unknown Object (File)
Wed, Dec 18, 9:43 AM
Unknown Object (File)
Mon, Dec 16, 11:30 PM
Subscribers
None

Details

Summary

ENG-9959.

  1. On success navigate to proper screen.
  2. Implement timeout from ENG-8226.

Depends on D14152

Test Plan
  1. Test adding device.
  2. Comment code on the secondary device to send confirmation, and test both removing and ignoring.
  3. Test other errors during flow like Identity call failure (link).

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.Thu, Dec 12, 12:20 PM

Will defer to @tomek on this one – I think it's probably a better bet for him to gain the context on QRAuthContextProvider than for me

It might be a good idea to have an effect that clears the timeout on unmount.

This revision is now accepted and ready to land.Fri, Dec 13, 6:32 AM