Refuses to allow key storage

[HarHarLinks]

Steps to reproduce

1. There is the prompt to allow key storage
2. Click Continue ("Fortfahren")
3. toggle the switch

Outcome

What did you expect?

key storage gets enabled

What happened instead?

the switch flicks back to off after clicking to enable it

Operating system

windows 11

Application version

Version von Element: 1.11.104 Krypto-Version: Rust SDK 0.11.0 (404ca47), Vodozemac 0.9.0

How did you install the app?

No response

Homeserver

synapse 1.131

Will you send logs?

Yes

[dbkr]

I'm not sure what switch you're referring to: this needs to be a lot clearer please. I'd guess the one in user settings / encryption but that has no 'continue' button.

Also, I don't see logs from you.

[HarHarLinks]

There is the prompt to allow key storage

top left corner popup toast thingy

Click Continue ("Fortfahren")

on said popup

toggle the switch

above button takes you to this page

with said switch at the top

[dbkr]

Ah, okay - thanks. If you can repro it again, please send logs.

[HarHarLinks]

I believe a rageshake was sent; this was on a device of someone I helped out getting set up, and we did rageshake several issue together. Look for a rageshake referring to "30228", not the whole github link.

[t3chguy]

There are no rageshakes referencing this issue which would make it very difficult to find the needle in the haystack of rageshakes.

[MightBeHarmless]

This issue also affects me, as described above.

First I encountered it using element v1.11.99 which is hosted by my homeserver operator. Incidentially, the Check for updates button is not functional, as it reports that I am at the latest version, when I was not.

So I signed in to app.element.io which is running v1.11.105, and reproduced the issue there. I was able to export logs and wlll attach them here, if I can figure out how to upload anything.

rageshake.tar.txt

remove .txt extension (its uncompressed)

Firefox 140.0.4 (64-bit) on Fedora 42

[dbkr]

error Unhandled promise rejection: Error: Error: Failed to decode Curve25519 key from Base64: Invalid number of bytes for Curve25519, expected 32, got 45

appears to be the problem, which is a bit concerning. Seems like we need to handle errors better. It would be interesting to know how it might have got into that state: have you used any other clients?

Incidentially, the Check for updates button is not functional, as it reports that I am at the latest version, when I was not.

This is something you'll need to report to your element web host as it's a fault with their setup.

[HarHarLinks]

While I don't know if the log I believed to have submitted contains the same issue, I can't answer how it broke either, but I can tell you

• only Element clients were used by the account in question, including desktop (windows), iOS legacy, iOS X, possibly android legacy at a point.
• as that account needed to reset their identity anyway (see also After resetting MY identity, Element claims OTHERS have reset their identity #30229), the issue with this switch happened to be resolved by doing so. this is only relevant because i would guess that resetting identity would regenerate the key in question from MightBeHarmless's log.

[MightBeHarmless]

HarHarLinks, If you wish to double-check if this log snippet also applies to you, I observed that you can open up the browser developer console. Try to trigger the "Allow key storage" button. You should observe an Error in the console, with this text right at the top line. This makes it easy for any user to spot check if they are experiencing this issue in the same manner.

Oh, did you point out that by resetting an identity, the issue no longer manifests?

This issue was first observed on 1.11.99 Element Web, confirmed to be following on 1.11.105 app.element.io. It was observed as I was unable to view the contents of one recently created encrypted room, that I joined just after the room was created and configured. The room may have had encryption enabled right from the start. I am unable to view my own messages as well as those from all others, but I can see basic room notices (join, invite, etc).

I also use the desktop Linux version of flatpak in.cinny.Cinny, which still permits me to see the contents of that room. Those are the extent of the clients I've tried through the period from when this room was created, messages created, and then becoming unable to view those messages. Maybe I was never able to view those messages on the Element Web clients.

So for the "Check for updates" button problem, you're saying this is a known issue that should not be reported here, as it has more to do with how they poll for updates or configured the instance? I won't make a new issue, if I have not already.