-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you launch the app from a push notif, you can be shown stale timeline with no spinner #4471
Comments
There is an issue in the state of the MXSession. What is happening behind the scene is that we start replaying Then, we do an incremental sync with the server. This is when the grey spinner appears. |
This |
We should probably merge all cached sync responses into one. It will kill the replay dance. |
As a quick workaround, can we show the catchup spinner until it's actually caught up? The worst thing here is that it's showing you stale content with no UI to warn you that it's stale. |
The catchup spinner will be fixed with the MXSession state fix. I have the feeling that merging all cached sync responses will improve the performance a lot. I cannot understand why the app stays so long in a stale state while everything is available locally. |
i'm getting this more and more, and it's taking so long to catch up it looks as if messages are missing entirely - with no spinner to tell you that you're looking at known stale content. |
After a few seconds messages start to be shown (still no spinner), and then after a few more seconds it catches up entirely - then briefly shows the grey spinner. This on 1.4.3 TF
The text was updated successfully, but these errors were encountered: