HomePhabricator
Diffusion Comm e8e641205114

[native] implement screen when secondary device is not responding

Description

[native] implement screen when secondary device is not responding

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

Reviewers: ashoat, tomek

Reviewed By: ashoat

Differential Revision: https://phab.comm.dev/D14152

Details

Provenance
kamilAuthored on Thu, Dec 12, 11:08 AM
Reviewer
ashoat
Differential Revision
D14152: [native] implement screen when secondary device is not responding
Parents
rCOMM7be865dbb8df: [native] add callback to remove secondary device during QR auth
Branches
Unknown
Tags
Unknown