Page MenuHomePhabricator

[native] implement screen when secondary device is not responding
ClosedPublic

Authored by kamil on Dec 12 2024, 11:34 AM.
Tags
None
Referenced Files
F5054206: D14152.diff
Tue, Mar 25, 5:31 AM
Unknown Object (File)
Thu, Mar 6, 2:54 PM
Unknown Object (File)
Thu, Mar 6, 2:53 PM
Unknown Object (File)
Thu, Mar 6, 2:53 PM
Unknown Object (File)
Wed, Mar 5, 3:32 PM
Unknown Object (File)
Mon, Mar 3, 6:22 AM
Unknown Object (File)
Feb 20 2025, 7:19 PM
Unknown Object (File)
Feb 18 2025, 9:14 AM
Subscribers
None

Details

Summary

ENG-9959.

Copy was discussed in ENG-8226#comment-dea392ea.

I am not sure how to solve this in terms of UX, the time when removing the device is pending:

  1. Like this, there might be a lag before navigating to Linked devices.
  2. Not await promise, but in this case user might see the device on the list, and will disappear after this promise is finished.
  3. Somehow show progress, but don't know how to handle the Ignore button then.

Also, swallowing errors here and just navigating to the Linked devices screen, we could show an Alert but wondering if this is worth it.

In ENG-9968 there is an example of how this looks like.

IMG_4790 (1).PNG (1×828 px, 57 KB)

Depends on D14151

Test Plan

Navigate to this screen

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.Dec 12 2024, 11:58 AM

Rahul has a graphic almost ready for this! We can either amend it here, or handle it later if it takes a bit before he can deliver the final version.

native/account/qr-auth/secondary-device-not-responding.react.js
57 ↗(On Diff #46387)

Nit

72 ↗(On Diff #46387)

Let's add a period at the end here

This revision is now accepted and ready to land.Dec 12 2024, 12:24 PM