-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UTD event was not decrypted after keys were received #4189
Comments
This is tracked on the EXA and EXI repos as element-hq/element-x-android#3747 and element-hq/element-x-ios#3449 respectively |
Possibly related: #3768 |
I think #3768 is not related. What I think is happening here is the following:
At least two (or now three) rageshakes were cases where the notification client received the room key. |
Would it make sense to have a generalization of |
We have that stream but it lives in the |
We could put it temporarily next to the crypto store cross-process lock, since it has to live in the |
Well the stream works this way:
We could move the stream out of the Of course the easy fix for EXA is to use the stream from the |
The keys to a given event arrived a few seconds after the event, but there doesn't appear to have been any attempt to retry the decryption.
The text was updated successfully, but these errors were encountered: