When no encryption keys are available, Seaglass should request keys and show dummy messages in the interim.
Actual Behavior
No message history seems to be shown, and eventually results in a crash as there is an inconsistency between the row count and an insert/remove operation on the room view table.
Steps to Reproduce the Problem
Remove all caches and MXFileStore
Log in and select an encrypted channel
Don't acknowledge keysharing requests from other clients, if any appear
Specifications
Expected Behavior
When no encryption keys are available, Seaglass should request keys and show dummy messages in the interim.
Actual Behavior
No message history seems to be shown, and eventually results in a crash as there is an inconsistency between the row count and an insert/remove operation on the room view table.
Steps to Reproduce the Problem