Element gets stuck on a "Continue" page of a SSO process of https://matrix.tedomum.net/ home-server when using Element for Android to sign into existing account registered on that home-server.
maksfastovets opened this issue · comments
Steps to reproduce
-
I created my new matrix account, and then a space, and a room in it on the https://matrix.tedomum.net/ home-server. I did all of that in a SchildiChat client on my MacOS.
-
Now when I am trying to sign into this my new acc using either SchildiChat or Element on my Android, I just cannot sign in.
-
Element opens emdedded, I believe, system browser with a SSO page of the https://matrix.tedomum.net/ home-server where I am able to input my credentials and click "Sign in" button, then page with "Continue" button appears, I click that "Continue" button, but I get stuck on that SSO sign in page, nothing just happens when I click on that "Continue" button.
-
There's no such issue with a desktop Element app for MacOS. On MacOs I can sucessfuly sign into that my acc with Element for MacOs.
Please see the screen capture (it is for SchildiChat, but behaviour in Element is just the same):
mx-tedomum-sso-issue.mp4
Outcome
What did you expect?
Using Element for Android app I expect to sign into that my account I registered on the https://matrix.tedomum.net/ home-server.
What happened instead?
Element for Android app opens emdedded, I believe, system browser with a SSO page of the https://matrix.tedomum.net/ home-server where I am able to input my credentials and click "Sign in" button, then page with "Continue" button appears, I click that "Continue" button, but I get stuck on that SSO sign in page, nothing just happens when I click on that "Continue" button.
Your phone model
Samsung A8 (2018)
Operating system version
Android 9
Application version and app store
Element v 1.6.5, PlayStore
Homeserver
Will you send logs?
Yes
Are you willing to provide a PR?
Yes
This homeserver uses SSO to sign in all of its services, so the issue was with Brave browse set as a default system one on my Android, and the issue was fixed when I used Firefox as a default sys browser.
So the issue can be closed.