Also removed an unnecessary check on the device ID being set, since the Flow types indicate it should always be set.
Depends on D12108
Paths
| Differential D12109 Authored by ashoat on May 20 2024, 3:54 AM.
Details Summary Also removed an unnecessary check on the device ID being set, since the Flow types indicate it should always be set. Depends on D12108 Test Plan I tested the flow using staging, with my phone as a primary device and a local simulator as a secondary device
Diff Detail
Event TimelineHerald added a subscriber: tomek. · View Herald TranscriptMay 20 2024, 3:54 AM2024-05-20 03:54:58 (UTC-7) Harbormaster completed remote builds in B29046: Diff 40383.May 20 2024, 4:10 AM2024-05-20 04:10:53 (UTC-7) This revision is now accepted and ready to land.May 20 2024, 5:37 AM2024-05-20 05:37:11 (UTC-7) Closed by commit rCOMM42ab4fd17086: [native][web] Fetch AES key and device ID in parallel in generateQRCode (authored by ashoat). · Explain WhyMay 21 2024, 1:11 AM2024-05-21 01:11:13 (UTC-7) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 40433 native/qr-code/qr-code-screen.react.js
web/account/qr-code-login.react.js
|
I don't think it is guaranteed that there will always be a response from the authoritative keyserver, e.g. when adding a new keyserver. We probably should add a condition here and extend a test plan to verify a non-auth keyserver auth.