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

[BillCarsonFr]

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.

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 performance when resetting backup.

After clicking on the continue button, there should be:

• Immediate feedback that the process has started
• A message saying that the page should not be closed or refreshed during this process (risk of keys never uploaded again until Element-R | Resetting key backup takes a long time; and blocks the whole application #26892 is fixed)
• Should lock the UX

Tasks

• Give feedback and warn user: Prevent user from accidentally triggering multiple identity resets #29388
• Lock out the UX

[mxandreas]

@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).

[uhoreg]

@americanrefugee The mockup at https://www.figma.com/design/ZodBLtGnKmRTGJo5SGLnH3/ER-137%3A-Excluding-Insecure-Devices?node-id=105-44947&t=Rv1KWawqmg3tAYOk-4 shows the button text saying "Reset in progress..." Should the button here show the same thing?

[mxandreas]

shows the button text saying "Reset in progress..." Should the button here show the same thing?

Yes, I think the Figma was just updated and the snapshot here went out of date.

[richvdh]

I wondered if "Lock out UX" was a critical part of this, but Andreas says (and I agree):

I think the lock out UX was probably just an initial idea (when the ticket was created), but I do not think it is worth investing any time into it before there is evidence that this is necessary.

So, #29388 is enough to close this.