We have a rageshake (https://github.com/element-hq/element-x-android-rageshakes/issues/2624) where there is clear evidence that an update to an Olm session has not been correctly persisted to the cache/store. This inevitably led to the Olm session becoming wedged, and subsequent UTDs.
I wonder if the update to the olm session was not correctly persisted to the in-memory cache? But then, I can't find the code that is meant to do that in the first place.
We have a rageshake (https://github.com/element-hq/element-x-android-rageshakes/issues/2624) where there is clear evidence that an update to an Olm session has not been correctly persisted to the cache/store. This inevitably led to the Olm session becoming wedged, and subsequent UTDs.