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
Following discussion in #10479 (and especially matrix-org/synapse#10479 (comment)), I've checked the sync response when Synapse does not have OTK (one time key) anymore. So when the number of OTK is changing from N to 0.
This issue has been migrated from #10484.
Following discussion in #10479 (and especially matrix-org/synapse#10479 (comment)), I've checked the sync response when Synapse does not have OTK (one time key) anymore. So when the number of OTK is changing from N to 0.
Instead of receiving
The client receives
"device_one_time_keys_count":{}
and so the client cannot distinguish "no change" and "no OTK left", and do not upload new OTK, which at the end breaks decryption of some messages.
Server version: 1.38.0 commit 12c92ee
The text was updated successfully, but these errors were encountered: