-
Notifications
You must be signed in to change notification settings - Fork 222
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
Sliding Sync does not seem to work #17651
Comments
"Sliding Sync is enabled by default in Synapse 1.114.0" refers to "Simplified Sliding Sync"
If you have a way to access the developer options before logging in, just do step 5. |
It reads like the worst possible UX. You first need to have the Sliding Sync Proxy for not depending on it then?! 😅 I wanted to avoid installing the sliding sync proxy in the first place. |
Note that currently released versions of Element X do need the proxy, this is more to support the upcoming releases which won't require them. We may have jumped the gun slightly by sticking it at the top of the changelog! |
Thanks for tha clarification @erikjohnston! I ran into the exact same problem as @immanuelfodor -- I'm excited to try Element X, but also can't install the sliding sync proxy. I guess I'll keep an eye out for future updates of Element X that will work without the proxy, now that my server's updated... |
I was so excited to try out sliding sync and then I saw this issue. Is this now just waiting on the Element X side or is there more needed in the Synapse side like for auth? |
Okay, so when is it going to be actually released and supported? As in:
|
I've just upgraded to version 1.7.5 of Element X which was released on the App Store just now for Apple devices, and it's working great! Thank you to for all the hard work that went into this, Matrix devs :-) @erikjohnston |
I see 6 open bugs with "sliding sync" in their names. So it's probably safe to say that sliding sync feature is now in beta tests phase and |
Element X Android 0.6.2 or so enabled simplified sliding sync by default, so this issue should be moot by now and can be closed? |
Yes this issue can now be closed. Both the Element X Android and iOS public builds have support for simplified sliding sync. |
Apparently, the docu is still saying the feature support is experimental:
|
Funny to repeat myself, another synapse release incoming and another 6 changes regarding sliding sync. I wonder if we are in beta test phase already or not quite there yet. It would really help to publish such information in release notes, we don't pay you so we don't care when it's done, but using an unstable feature on production for unestimated period is not the greates idea. Is it at least safe to use pre-v1.114.0 synapse versions to be sure that none of these bugs affects stability or performance of the instance? |
We do not consider sliding sync to be in beta nor a test phase, and expect incremental improvements to happen just like we do with Synapse as a whole. On your point re Synapse versions, I would recommend using the latest stable (non-rc) version of Synapse. |
Im not sure where to ask, so I apologize for kinda hijacking this. But its still not working for me. I am on Synapse 1.116 and Element X 1.8.4 and its just saying that it cant connect to my homeserver every time. Is there any documentation how to successfully get sliding sync working somewhere? Edit: Ive found the issue. Element X does not support TLSv1.3. Guess Ill see if there is an issue open for it already, because its a bit strange for the new client to not support this. |
Not to my knowledge, no. I've had some successful experiments but it was rather cumbersome and mostly trial-and-error, so we could say that's not a mature and documented process. Currently waiting to get the feature stabilised so maybe I try again, until then using SimpleX for fun, as there are no integration issues there. |
There is no documentation as there is none needed. Recent synapse servers have it built in and enabled by default. So have the 'X' clients. Support for the separate sync proxy is fading out and to be removed completely. As to that, there is nothing experimental if you are on recent versions. As to TLS 1.3, I doubt that this is the issue. I run a server on a TLS 1.3 setup just fine. But that might depend on your Android version, so older versions could have problems there. |
It is TLS1.3 |
Uhh, interesting, thanks. Will need to check if it falls back to TLS 1.2 for me then. Anyway, not part of this issue. |
https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/ Ahh, finally we learn that MSC3575 is basically dead and replaced with MSC4186 which requires no user action, is not yet supported by element-web (which instead includes a confusing message saying "your server lacks support") and is basically in beta until 17.01.2025. If only we knew before, so much time waste could have been avoided. |
For anyone else who, as myself, did not understand if Simplified SS is or is not supported in Element Web/Desktop (i.e. not X), an answer: element-hq/element-web#28736 My understanding is:
If I am wrong, please correct me. |
Nearly correct, yes:
|
Description
Release notes mention that Synapse 1.114.0 enabled Sliding Sync by default:
I've upgraded Synapse and tried logging in with Element X.
It just tells me something like "This homeserver does not currently support SlidingSync.".
Steps to reproduce
Homeserver
erebion.eu
Synapse Version
1.114.0
Installation Method
Docker (matrixdotorg/synapse)
Database
Postgres, single container
Workers
Single process
Platform
Debian Stable
Configuration
No response
Relevant log output
There's nothing in the logs that I can find.
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: