Differential D15221

[native] refetch platform details when keeping secondary that is not responding
ClosedPublic
Actions

Authored by kamil on Aug 20 2025, 11:05 AM.

Details

Reviewers

bartek

Commits

rCOMM3797f8d7e082: [native] refetch platform details when keeping secondary that is not responding

Summary

ENG-11140.

Test Plan

Add code trigger timeout
Add secondary device
On timeout, select option to keep the device
There is no question mark next to device

Diff Detail

Repository

rCOMM Comm

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

kamil created this revision.Aug 20 2025, 11:05 AM

kamil held this revision as a draft.

Herald added subscribers: tomek, ashoat. · View Herald TranscriptAug 20 2025, 11:05 AM

kamil published this revision for review.Aug 20 2025, 11:06 AM

Harbormaster failed remote builds in B35325: Diff 49609!Aug 20 2025, 11:06 AM

CI issues can be ignored, this is caused by ENG-11110

bartek accepted this revision.Aug 20 2025, 11:14 AM

This revision is now accepted and ready to land.Aug 20 2025, 11:14 AM

This revision was landed with ongoing or failed builds.Aug 20 2025, 11:23 AM

Closed by commit rCOMM3797f8d7e082: [native] refetch platform details when keeping secondary that is not responding. · Explain Why

This revision was automatically updated to reflect the committed changes.

kamil added a commit: rCOMM3797f8d7e082: [native] refetch platform details when keeping secondary that is not responding.

Revision Contents
Changeset List

Path

Size

native/

account/

qr-auth/

secondary-device-not-responding.react.js

28 lines

Diff 49612

View Options

native/account/qr-auth/secondary-device-not-responding.react.js

[native] refetch platform details when keeping secondary that is not respondingClosedPublicActions