Restore from backup failure after backup has been re-created from another session

[BillCarsonFr]

Steps to reproduce

1. Create a new account from web
2. Set up secure backup (eventually create an e2ee room with some messages to have something to backup)
3. Keep the created session and use another private/context tab to log in the same account from another web
4. Verify the second session using the passphrase from 2
5. On the second session, go to Settings > Security & Privacy and then delete the backup
6. Still on the second session create a new backup (you will be prompt to enter passphrase again)
7. Now go back to the first session
8. go to Settings > Security & Privacy and then tap on Restore from backup.
9. Enter the passphrase

Actual:
After you entered sucessfully the passphrase you'll see this dialog

It looks like the legacydialog to enter the megolm backup key (not the 4S)

Expected:
It should just import your keys.

Worth Noting:
If you go back and try again to restore from backup it will work.

Notes:
It's a case of desynchronised 4S and local cached key. When you try to restore you already have a megolm backup key known locally in cache but it's outdated.

Outcome

What did you expect?

What happened instead?

Operating system

macOS

Browser information

FF

URL for webapp

develop.element.io

Application version

Element version: 850a250-react-3e31fdb6a71f-js-d190cdc307f1 Olm version: 3.2.8

Homeserver

local synapse

Will you send logs?

No

[richvdh]

I wonder if this is still a thing. Given most of the code has been rewritten, it may well not be. We should re-triage it.

[richvdh]

I think this is actually a duplicate of #27469.