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
Suppose a message arrives before its decryption keys. It is initially shown as "Waiting for this message".
If the key is then received by the NotificationClient, rather than the main client, it looks like we do not update the UI to show a successful decryption.
(Closing and reopening the client fixes the problem.)
It might do with the fact that we don't use the OlmMachine stream to listen to newly arrived room keys, instead we listen for m.room.key events on the Client and if we receive that event on the notification client we miss that?
Suppose a message arrives before its decryption keys. It is initially shown as "Waiting for this message".
If the key is then received by the
NotificationClient
, rather than the main client, it looks like we do not update the UI to show a successful decryption.(Closing and reopening the client fixes the problem.)
Rageshake: https://github.com/element-hq/element-x-android-rageshakes/issues/2885
The text was updated successfully, but these errors were encountered: