Element keeps loosing my Rooms #5924
Comments
noantiq
added
the
T-Defect
pixlwave
added
A-Room-List
S-Critical
|
There's a possibility the cause of this is related to #5930 given there's a rageshake mentioning both duplicate rooms and a lot of missing rooms at the same time. |
|
Have the same problem on homeserver |
|
I noticed this issue as well Element iOS will randomly lose encryption keys and room data. I have been fixing it by reinstalling the app and logging back in. I suggest having a second device to verify until this bug is resolved. |
|
As mentioned in #6136, this can apparently happen after opening element on a poor connection. |
|
It is happening quite frequently to our iOS app, almost every day for some users. It happens nearly every time on low connection and on 4g network. We used to use Matrix SDK version 0.22.0 and had this issue, so we thought upgrading the SDK could solve the issue but updating the SDK to 0.23.4 didn’t work out. When rooms are gone, the user has to wait 10mins to max up to 1 hour to get the chats back without signing out and signing in. But if sign out and sign in can see the chats, as a quick way of restoring his chats, but cannot tell them to do so every day. It's pretty embarrassing to get back to the users with no answer about this! Please let us know if we are needed to participate to solve this issue. |
|
As an update, it happens on WIFI and very good connection too. So the theory of poor connection seems to be invalid. On a good connection, but after reopening our app (causes an init sync) the chats are back so no need to re-login. |
|
It doesn’t depend in connection. We have the same issue on home server. I am admin and I don’t have this problems. But I don’t have a lot chats. Other members have this issue. The chat a lot and have many rooms. More than 5. |
|
Which version of synapse you are using @ChzenChzen? As I noticed from the discussion and bug reports, it started happening from 1.55.2. am I right? |
|
@mehrshadJalilmair I don't know precise. But I had updated the server a couple of weeks ago, and this bug still exists. |
|
@ChzenChzen OK! I hope this will be solved soon. But I'm pretty sure it started happening after upgrading our synapse server. |
|
Hello everybody 👋 Unfortunately this problem is turning out quite difficult to reproduce, not to mention track down and fix. I have built a new testflight version 1.8.15 (20220518170737) in which I've reverted some commits that might have introduced it. Please don't use any other version for this as it won't contain the intended changes. Please help us test it and do let us know if you can still reproduce the problem. If you can try changing the search filters at the top or restarting the app to see if they have any effect. Thank you! |
|
Thanks @stefanceriu for the update. I'll be testing this TF version. maybe I connect to our servers too, can I? |
Sure thing, feel free to use it with any homeserver. |
|
@stefanceriu Using the TestFlight version you posted above, I am able to reproduce all the issues I had seen before on a daily basis, which include #5924/#6006 but also #5930 (which I assume is related). Took about 2 hours of to occur (I am an active user). This is on a custom homeserver hosted by Element Matrix Services. Many of our users are experiencing these issues. Clearing cache still is a valid workaround. It is very easy for me to repro this, and I would be very happy to help in the resolution since this affects me on a daily/hourly basis. I am familiar with iOS development and can capture logs if needed. I can't currently get an Xcode development setup to build my own version of the app for experimentation though (plus I cannot afford to lose the state of my client since this is a production environment) |
|
Uf, that's dissapointing 😔 Thank you for looking into it. No need to setup you enviroment but do please send us a rageshake with logs (settings/report bug) when you see it next time. |
|
@stefanceriu I'm not sure I'll be able to send unreviewed logs since this is a sensitive corporate workspace. is there an option to review/censor logs before sending? |
|
I'm afraid not, no. |
|
@stefanceriu are there any logs that are emitted to system log which can help with root cause analysis? |
|
I don't think so but even if they were we usually need to sift through a lot of them to figure out what's wrong. No worries though, we're on it. |
|
@stefanceriu two notes: (1) If you need a tester for #1475 I'll be happy to help and have an easy time repro'ing (2) to me it feels that #5924 and #5930 are very related because they occur together and both seem to be the result of some messed up local caching |
|
Yes please 🙇 . We'll let you know when it's available in a build. |
|
@stefanceriu @ismailgulek is this supposed to be fixed in 1.8.17 Testflight build? I can still reproduce #5924/#6006 and #5930 in that build with similar frequency as before EDIT Sorry I missed the second PR 1485 - will wait for a version that includes both |
Hey @matrixuser0, sorry to hear that. We tried to have a workaround for this issue that we couldn't reproduce reliably. Still working on the issue. And i think our workaround doesn't affect #5930 |
|
I used to be able to reproduce this very regularly (multiple times per day) up until 1.8.17. I have not experienced this with 1.8.18 Testflight build yet after multiple days - same is true for #5930 |
Steps to reproduce
Outcome
What did you expect?
My rooms, spaces and DMs are visible
What happened instead?
Your phone model
iPhone 8
Operating system version
iOS 15.4
Application version
Element 1.8.8
Homeserver
Synapse 1.55.2
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: