Page MenuHomePhabricator
Differential D12123

[native] Handle outdated client error in QR code auth flow
ClosedPublic
Actions

Authored by ashoat on May 20 2024, 6:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jun 26, 10:00 PM
Unknown Object (File)
Thu, Jun 20, 4:57 PM
Unknown Object (File)
Thu, Jun 20, 4:57 PM
Unknown Object (File)
Thu, Jun 20, 4:57 PM
Unknown Object (File)
Thu, Jun 20, 4:55 PM
Unknown Object (File)
Thu, Jun 20, 8:45 AM
Unknown Object (File)
Thu, Jun 20, 12:04 AM
Unknown Object (File)
Wed, Jun 12, 2:43 AM
View All 23 Files
Subscribers
tomek

Details

Reviewers
bartek
Commits
rCOMMa00d4c26e2b8: [native] Handle outdated client error in QR code auth flow
Summary

I originally noticed that the QR code flow didn't handle this error when investigating ENG-8113. That led to the further realization that the QR code flow hasn't been kept up-to-date, which was addressed in ENG-8123. This diff completes the circle and finally adds code to handle the outdated client error specifically.

Depends on D12116

Test Plan

I tested the web equivalent by hardcoding a failure in keyserver/src/session/version.js for all web clients

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Revision Contents
Changeset List

PathSize
native/
qr-code/
23 lines

Diff 40440

View Options

native/qr-code/qr-code-screen.react.js

Loading...