You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logs in the receiver side show a pattern like this:
2025-01-20T15:46:43.519041Z Failed to decrypt a room event
... (9 more Failed to decrypt)
2025-01-20T15:46:46.398276Z Failed to decrypt a room event
2025-01-20T15:46:46.407885Z Received a new megolm room key
2025-01-20T15:46:46.418528Z Failed to decrypt a room event
.. (2 more Failed to decrypt)
So the megolm key arrived at almost the same moment as the events.
There is no mention of "Retrying decryption" anywhere in the receiver logs.
I am wondering whether the async task pulling from room_keys_received_stream() might have retried decryption too early, before the incoming batch of events was finished processing?
The text was updated successfully, but these errors were encountered:
Steps to reproduce
See this rageshake: https://github.com/element-hq/element-x-android-rageshakes/issues/4076
The logs in the receiver side show a pattern like this:
So the megolm key arrived at almost the same moment as the events.
There is no mention of "Retrying decryption" anywhere in the receiver logs.
I am wondering whether the async task pulling from
room_keys_received_stream()
might have retried decryption too early, before the incoming batch of events was finished processing?The text was updated successfully, but these errors were encountered: