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.

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

Encryption Settings | Reset Identity can take long if there are a lot of keys and there is no feedback, and possible to click the button several times #29192

Open
Tracked by #2700
BillCarsonFr opened this issue Feb 5, 2025 · 1 comment
Labels
A-E2EE 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

BillCarsonFr commented Feb 5, 2025

Actions

  • Add a spinner when you click Continue as per the comment below

Description

Given an account with at least 20k keys cached and uploaded to an exisiting backup.

If you go to Settings > Encryption then click Reset cryptographic identity and then continue.

Image Image

Actual

Nothing will happen for 15/20s. There is no feedback that the reset process has started.
You can click several times on the continue button, this will lead to a broken state were you will be asked to enter account password several times.

Expected

This is due to an existing issue with indexeddb performances when resetting backup.

After clicking on the continue button, there should be:

@dosubot dosubot bot added A-E2EE A-Storage Storage layer of the app, including IndexedDB, local storage, etc. 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 5, 2025
@mxandreas
Copy link

@americanrefugee Has proposed the following designs. These will be used to mitigate the issue short-term until the performance issue gets solved (it could be that this is useful even the performance gets improved).

Image

@dbkr dbkr removed the A-Storage Storage layer of the app, including IndexedDB, local storage, etc. label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE 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
Development

No branches or pull requests

3 participants