![]() Corrupted OlmSessions riot-android#799 (fixed, but you may still have broken Olm sessions because of it).network blips during device key download stop megolm key-sharing working #2562.We sometimes fail to decrypt events which arrive in the initialsync #2273.Make sure we process to-device messages before generating new one-time-keys #2782.Check that device list is updated correctly when encryption is turned on in a room #2672 / Stale device lists #2305 / device list update is *still* racy #3796 / e2e : Stale device lists element-ios#955 (fixed riot-ios 0.5.0) / E2E: Stale device lists riot-android#863 (fixed riot-android 0.6.10).Race in decrypting events causes UISI #5001 (fixed riot-web 0.12.5).Stale device lists when users re-join e2e rooms #4983 / Decrypt error related to new device creation matrix-org/matrix-ios-sdk#340 / Stale device lists when users re-join e2e rooms riot-android#1603.Stuck in a loop generating and failing to upload one-time keys #4216 / Stuck in a loop generating and failing to upload one-time keys riot-android#1289 / Stuck in a loop generating and failing to upload one-time keys element-ios#1256.different devices with the same curve25519 key confuse the olm layer #3231 (also on android/ios).prioritise established olm sessions over half-open ones #2783 (also on android/ios).We can still throw away one-time keys which have messages in-flight #3309 (also on android/ios).Olm is prone to race conditions across multiple tabs #2325.This is definitely by design, though see Improved communication to recipient that the sender didn't want you to see their message #3831 for improving visibility on this. The sender has blacklisted your device.element-meta#647 and Let megolm session keys be available to invited users since the point they are invited #2713 are relevant. This is sort-of by design, though Hide undecryptable messages which predate your device's participation in a e2e room #2258, Let devices request keys to decrypt past history for a room. You logged into your device, or joined the room, after the message was sent.This bug serves as a reference to the reasons we know about. This message (or, less often, the closely related "OLM.UNKNOWN_MESSAGE_INDEX") can be caused by a number of things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |