marwing

I noticed this for another user ([@cyberes:evulid.cc](https://matrix.to/#/@cyberes:evulid.cc)) today:  I sent logs again with a link to this issue.

I just noticed this again on the latest TF build (1.5.1) with sliding-sync proxy v0.99.13 and synapse v1.98.0. Once again with a different user and this time also in a...

Sent some more logs for another case. Event: https://matrix.to/#/!ehXvUhWNASUkSLvAGP%3Amatrix.org/%24iMCI3gJow1Xsizo1L08Vn1l2hxv3MEXN9qL-2QcHkHU  @kittykat What additional info do you need? Anything I can provide?

This is more relevant than ever now that spaces are here and a supported way to explore new rooms.

Not sure if this applies to this specific case, but for me search is case-insensitive when fuzzy search is turned off (in dev settings, default), but becomes case-sensitive if at...

I tried but failed to send logs (see #4185 for details). If you need logs for this, please let me know and I'll try to find and send them manually...

I would likely agree with your argument, particularly in light of https://github.com/element-hq/element-x-ios/issues/4177, which, if I interpret it correctly, breaks partially reading a room worse than it was before (something I'm...

This was not actually fixed, I just verified with the nightly TF build. The issue is that the marker is rendered at the wrong location (some messages newer than it...

I'm now blaming this on iOS after observing this today, unless someone has a reason to do otherwise. The way the icons fix themselves feels like a notification ui bug...

I'm closing this now. Somehow this seems to have stopped happening and I don't see the app having much to do with that. (Even though the SDK and notification updates...