-
Notifications
You must be signed in to change notification settings - Fork 232
Cleanup OIDC #1128
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
Cleanup OIDC #1128
Conversation
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
Kudos, SonarCloud Quality Gate passed! |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #1128 +/- ##
========================================
Coverage 57.10% 57.10%
========================================
Files 1023 1023
Lines 26243 26243
Branches 5309 5309
========================================
Hits 14987 14987
Misses 8946 8946
Partials 2310 2310
☔ View full report in Codecov by Sentry. |
// consider that the user has cancelled the login | ||
// by pressing back or by closing the Custom Chrome Tab. | ||
lifecycleScope.launch { | ||
delay(5000) |
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.
Why the 5s delay here?
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.
This is sort of a compromise... If we wait more, the user will see a disabled button for a longer time.
If we wait less, we take the risk to cancel the login operation (the request to the homeserver with the Oidc token) before it finishes. The request does not take a long time, so maybe 2s is enough, but I did not want to take the risk.
The solution is not ideal, maybe we could try to detect that no OidcAction has been triggered (this should happen quite faster) and if this is the case we can cancel faster. I will think again about it.
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.
LGTM, thanks!
Take into account comment from #1127 PR
Add a workaround to prevent user from getting stuck on a disabled "Continue" button.
(manually assigned to @jmartinesp for the follow up on #1127)