-
Notifications
You must be signed in to change notification settings - Fork 160
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
Fix new logins with Simplified SS using the proxy #3417
Fix new logins with Simplified SS using the proxy #3417
Conversation
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3417 +/- ##
========================================
Coverage 82.61% 82.61%
========================================
Files 1694 1694
Lines 39685 39685
Branches 4831 4831
========================================
Hits 32787 32787
Misses 5205 5205
Partials 1693 1693 ☔ View full report in Codecov by Sentry. |
val slidingSync = when { | ||
AuthenticationConfig.SLIDING_SYNC_PROXY_URL != null -> ClientBuilderSlidingSync.CustomProxy(AuthenticationConfig.SLIDING_SYNC_PROXY_URL!!) | ||
appPreferencesStore.isSimplifiedSlidingSyncEnabledFlow().first() -> ClientBuilderSlidingSync.Simplified | ||
restore -> ClientBuilderSlidingSync.Restored |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we not checked first if restore is true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooops, true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix, I've not tested but looks ok!
Quality Gate passedIssues Measures |
Content
Setup whether to use the proxy or native sliding sync at an earlier stage when signing in, so the
SlidingSyncVersion
is properly populated, stored and later restored.Motivation and context
With the current code, Simplified Sliding Sync was never used even if it was enabled in developer options.
Tests
/sync
requests hit the right endpoint (_matrix/client/unstable/org.matrix.simplified_msc3575/sync
instead of_matrix/client/unstable/org.matrix.msc3575/sync
)./sync
requests.Tested devices
Checklist