Unable to decrypt: The secure channel with the sender was corrupted. Trying to create a new secure channel and re-requesting the keys. #12250
Comments
|
Also ran into this issue on chromium 80.0.3987.132. debug logs have been sent |
|
I'm seeing this more and more as well... |
|
Killed the . Re-importing an exported e2e keyset from device #2 (Android, which still works flawlessly) and importing with Device #1 does not change the fact. Pressing the 1.6.2 |
|
I'm encountering this error message in a room. It turns out I have two of my own accounts connected to this room, and one of my accounts cannot read the messages sent with the second account. I sent rageshakes from Element-web from both sides. Both accounts are connected using Element-web 1.11.37, and both also with Element-android (1.6.3 in one case and 1.6.5 in the other, Rust SDK 0.6.0 in both cases). |
|
Nobody has had time to investigate the rageshakes, but likely due to one of the causes already listed at element-hq/element-meta#245. |
* Use h1 as first heading in dialogs The dialog should be modal and therefore the only content active on the screen, so the title of the dialog should be the top level. Update snapshots & tests appropriately. * Just customise the letter spacing on dialog titles
Description
Got a random "Sender hasn't sent us the keys for this message" incoming message on Riot iOS during one of my 1-1 chats, so I fired up one of my riot web instances to check the room there, and instead was greeted with the message in the title (and messages that I could decrypt on iOS are not able to be decrypted on riot web). Logs will be attached to this issue.
Steps to reproduce
Was having a conversation in a long-running e2ee 1-1 room with a friend from riot iOS, got an unable to decrypt, fired up riot web, got corrupt session errors.
Version information
riot iOS v0.10.4
riot-web develop (c3e6a30-react-73b177d07567-js-312976294b7e)
For the web app:
The text was updated successfully, but these errors were encountered: