Cannot decrypt old message #20461
Labels
A-E2EE
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Critical
Prevents work, causes data loss and/or has no workaround
T-Defect
Z-UISI
Unable to decrypt errors
Comments
kittykat
added
T-Defect
S-Critical
|
Was the message sent while you were logged out of all sessions? |
No, I was logged in and actively talking to the other person. I also can't decrypt my own messages that I sent in that conversation. |
|
Can you sign in in another session where you verify with a security key? Does that decrypt your messages? |
|
Maybe caused by #20699 |
|
Closing in favor of #21026 for lack of other clues. |
25 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On web, I have an old message (
"event_id": "$lrfVE548vZdC2mVJjoXiGkyBl8PiJdWq2RPRyxp3dPU") which is encrypted and I get an option to request keys from other sessions:I can re-request keys and the UI says that the request is sent:
But on Android, I don't see the chat in the correct place in my history and I get a
** Unable to decrypt: The sender's device has not sent us the keys for this message. **error for the message.I don't have any other sessions running that have this message decrypted as far as I'm aware. I don't think it's a time issue as I've been waiting for it to be decrypted for a while.
Steps to reproduce may include logging out of all sessions and then restoring keys via a security key and then resetting the security key as well at some point.
I'm triaging as S-Critical because I haven't been able to retrieve some information that I need to get from a chat backlog.
O-Occasional because this is happening in every encrypted chat that I have for ~November.
The text was updated successfully, but these errors were encountered: