Page MenuHomePhabricator

[lib] Stop attempting recovery when client version unsupported
ClosedPublic

Authored by inka on Apr 11 2024, 5:04 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jun 24, 4:59 AM
Unknown Object (File)
Mon, Jun 24, 4:59 AM
Unknown Object (File)
Mon, Jun 24, 4:59 AM
Unknown Object (File)
Thu, Jun 20, 2:26 PM
Unknown Object (File)
Mon, Jun 17, 4:15 AM
Unknown Object (File)
Sun, Jun 16, 10:01 PM
Unknown Object (File)
Sat, Jun 15, 6:54 AM
Unknown Object (File)
Fri, Jun 14, 8:15 AM
Subscribers

Details

Summary

issue: ENG-6125
If the client got client_version_unsupported, a recovery will not help them, so we should skip it. We should just set the session change sent by the server, and a connectionIssue so that other places in the code know what the problem was.

Test Plan

Tested that if the auth keyserver sends client_version_unsupported, then the user is logged out. Checked that a connectionIssue was set, and that triggered the logout.
I tested in the multikeyserver setup, that if the second keyserver sends client_version_unsupported, then the client is not logged out, and a popup shows up. For now, this results in the screen being spammed with popups, because ENG-5913 was not implemented yet (only in case of the secondary keyserver).

Diff Detail

Repository
rCOMM Comm
Branch
inka/client_version_unsupported
Lint
No Lint Coverage
Unit
No Test Coverage