Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Recovery Method modal shows on screen with unexpected timing, an outdated message and button text is a bit off? #29171

Open
Tracked by #2700
BillCarsonFr opened this issue Feb 4, 2025 · 0 comments
Open
Tracked by #2700

New Recovery Method modal shows on screen with unexpected timing, an outdated message and button text is a bit off? #29171

BillCarsonFr opened this issue Feb 4, 2025 · 0 comments
Labels
A-E2EE-Key-Backup O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@BillCarsonFr
Copy link
Member

Related to #29170 as it is same step to reproduce.

The recovery key has been changed by another EX client.
Web is not reacting about it at all.

But long after, if you send a new message, suddenly there is this popup:

Image

This appears to be triggered following an error when trying to upload key to backup

[PerSessionKeyBackupDownloader] Got current backup version from server: 25
rageshake.ts:69 [PerSessionKeyBackupDownloader] Version for which we have a decryption key (24) doesn't match the version we are backing up to (25)

Expected

I would have expected this popup to show just after the recovery was reset, instead of after sending the next message.

I would have expected to have a Yes it was me button?
Not sure to see why there is a Set up secure message? As per the text on the modal I should reset everything (including the account password?)
@dosubot dosubot bot added A-E2EE-Key-Backup O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect labels Feb 4, 2025
@mxandreas mxandreas mentioned this issue Feb 4, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE-Key-Backup O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BillCarsonFr