Page MenuHomePhabricator

[native] implement screen when scanning QR code a non-primary device
ClosedPublic

Authored by kamil on Dec 11 2024, 8:15 AM.
Tags
None
Referenced Files
F5026272: D14114.id46549.diff
Mon, Mar 24, 11:45 AM
F5025878: D14114.id46332.diff
Mon, Mar 24, 7:45 AM
Unknown Object (File)
Wed, Mar 19, 11:08 AM
Unknown Object (File)
Sat, Mar 15, 12:21 AM
Unknown Object (File)
Sat, Mar 15, 12:21 AM
Unknown Object (File)
Sat, Mar 15, 12:20 AM
Unknown Object (File)
Sat, Mar 15, 12:20 AM
Unknown Object (File)
Fri, Mar 14, 6:22 AM
Subscribers
None

Details

Summary

ENG-9959.

Copy is taken from ENG-9936

Styles are taken from similar register screens, and there is a chance that those will duplicate with other QR Auth screens - if so I am going to refactor this but for now I prefer to keep this like this if there are any changes needed specific to a screen.

Also, after this is done maybe worth renaming the <Registration* components to <Auth* components to avoid confusion.

In ENG-9968 there is an example of what the flow looks like.

IMG_375B92D671D6-1.jpeg (1×828 px, 130 KB)

Depends on D14105

Test Plan

Navigate to screen

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil added inline comments.
native/account/qr-auth/qr-auth-not-primary-device.react.js
57 ↗(On Diff #46332)

This probably needs to be updated as this is not taking user back (to camera) but to Linked Devices screen

kamil published this revision for review.Dec 11 2024, 8:29 AM
ashoat added inline comments.
native/account/qr-auth/qr-auth-not-primary-device.react.js
57 ↗(On Diff #46332)

Not sure it matters a ton

This revision is now accepted and ready to land.Dec 12 2024, 10:58 AM