"Unable to decrypt: The sender's device has not sent us the keys for this message."

[claell]

Steps to reproduce

1. Use element before
2. Use encrypted messages
3. Register a new device (element web in my case)

Outcome

What did you expect?

Messages should display normally

What happened instead?

I get the error in the title. Clicking "retrieve keys from other sessions" doesn't work, either.

Operating system

Windows

Browser information

Firefox

URL for webapp

app.element.io

Application version

No response

Homeserver

matrix.org

Will you send logs?

Yes

[claell]

Other important information:
Screenshot:

Also, I just set up fluffychat on the same device and did not experience this problem there (the same chats can be decrypted there). So I am rather sure this is a bug of element.

Umbrella issue for those problems: #2996
Unfortunately, I am not experienced enough (and currently also don't have the time) to say whether this issue is a duplicate of one of the issues listed there.

[claell]

Not sure, possibly matrix-org/matrix-js-sdk#1866 is the cause for this?

[claell]

Hm, out of curiosity, I just signed in on develop.element.io. Then I verified that device from app.element.io (at least I think so, I also needed to type in the security phrase). But then on develop.element.io, I was notified that the app.element.io session still needs verification (which is weird). After I verified app.element.io from develop.element.io, I now could also read the chats there that were previously unable to decrypt. Not sure what caused this (for example, I am rather sure that I have verified app.element.io before, but maybe there went something wrong during that process).

[claell]

And now I think that I get the error again for the two most recent messages on develop.element.io (which I think decrypted fine some minutes before). At least the option to request the keys from another session does seem to work for them.

[claell]

For another room, it first showed the error for a short time and then displayed most of the messages correctly. However, the error stayed there for some messages. There I had to manually request the keys from another session.

[kittykat]

@claell can you please submit rageshakes (logs) from app.element.io, develop.element.io and the device that you originally tried to verify app.element.io against?

You can submit rageshakes from the settings on all devices, or by sending /rageshake in any room in the web client.

[claell]

@kittykat Thanks, just sent them for app.element.io and develop.element.io. I am not sure which device I originally (tried?) to verify app.element.io against. Possibly my mobile phone or I used the security phrase without a second device. Unfortunately, I didn't find the log sending option on Android and also /rageshake was not recognized there (although the functionality should be there according to element-hq/element-android#33 or am I wrong?).

[kittykat]

You can enable rageshakes in the advanced settings and then literally shake your phone to trigger it:

[claell]

Lol, it is a bit weird that only this option works and both other options (menu or command) are not available for sending stuff. I guess I'll create an issue for that.

[claell]

BTW: I didn't have to enable it, it was already enabled for me. Just didn't shake my phone before, as I wasn't familiar with the concept of rageshake before.

[claell]

Logs for Android device are also sent out now. I mentioned the number of this issue in the description.

[claell]

Followup issue for rageshake on mobile: element-hq/element-android#4881

[waclaw66]

Probably the same as #19748. Try to use passphrase instead of verifying device. If it helps, it's definitely the same bug.

[claell]

Might be true. However, the behavior is strange. At first, clicking the button to retrieve the keys from another device did nothing. Later, on develop.element.io, it works (but sometimes does not decrypt all messages in a chat). Possibly I am also experiencing more than one bug, which then makes it harder to determine which one it is.

[richvdh]

this seems to have gone stale. closing in favour of element-hq/element-meta#245.