Page MenuHomePhabricator

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

Authored by ashoat on May 20 2024, 6:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 8, 3:10 AM
Unknown Object (File)
Fri, Nov 1, 1:57 PM
Unknown Object (File)
Fri, Nov 1, 1:57 PM
Unknown Object (File)
Fri, Nov 1, 1:57 PM
Unknown Object (File)
Fri, Nov 1, 1:57 PM
Unknown Object (File)
Oct 19 2024, 9:47 AM
Unknown Object (File)
Oct 19 2024, 9:40 AM
Unknown Object (File)
Oct 19 2024, 9:32 AM
Subscribers

Details

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