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.
Details
Details
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
Diff Detail
- Repository
- rCOMM Comm
- Branch
- inka/client_version_unsupported
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
Comment Actions
I can review this one, since I wrote the original code that dispatches setActiveSessionRecoveryActionType