if we're trying to add a device from an iOS simulator or android emulator, we should just display a TextInput where the user can paste the QR Code URL
Depends on D12619
Paths
| Differential D12620 Authored by varun on Jun 28 2024, 12:58 PM.
Details Summary if we're trying to add a device from an iOS simulator or android emulator, we should just display a TextInput where the user can paste the QR Code URL Depends on D12619 Test Plan if device is added successfully, we are navigated back upon acknowledging the alert if device can't be added successfully, we are navigated back when the alert fires adding keyserver as secondary device works -- appears in DDB correctly
Diff Detail
Event TimelineHerald added a subscriber: tomek. · View Herald TranscriptJun 28 2024, 12:58 PM2024-06-28 12:58:31 (UTC-7) Harbormaster completed remote builds in B30007: Diff 41821.Jun 28 2024, 1:13 PM2024-06-28 13:13:59 (UTC-7)
Comment Actions Love some of the improvements you made to the existing code, such as passing more specific data into the hooks Requesting chnages for some questions, and to remove the button for non-emulators
This revision now requires changes to proceed.Jul 1 2024, 5:25 PM2024-07-01 17:25:00 (UTC-7)
Harbormaster completed remote builds in B30295: Diff 42243.Jul 11 2024, 3:34 PM2024-07-11 15:34:48 (UTC-7) This revision is now accepted and ready to land.Jul 11 2024, 9:19 PM2024-07-11 21:19:27 (UTC-7)
Closed by commit rCOMM63899045a319: [native] modify SecondaryDeviceQRCodeScanner to support emulator (authored by varun). · Explain WhyJul 12 2024, 12:19 PM2024-07-12 12:19:26 (UTC-7) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 41821 native/profile/linked-devices-header-right-button.react.js
native/profile/profile.react.js
native/profile/secondary-device-qr-code-scanner.react.js
native/utils/alert-messages.js
|