Open nisbet-hubbard opened 1 year ago
@nisbet-hubbard I've tested it and the app will timeout after 40-seconds and show the server selection screen. There has to be some timeout period for it to determine that matrix.org is unreachable as you could be on a bad connection.
I've updated this issue to reflect that the timeout should be reduced.
Thanks @pixlwave!
If the purpose is to test for bad connection, surely it applies equally to non-matrix.org homeservers?
For better UX, could we use something like what FluffyChat does? Namely, let the user choose a homeserver upfront and do the timeout test on whichever homeserver they've chosen.
Unfortunately the majority of our focus is on Element X now, so this is unlikely to receive any time over here. But I think the EX flow might be more suitable for the suggestion.
Steps to reproduce
Where are you starting? What can you see?
The startup screen. In a geography where matrix.org is blocked.
What do you click?
‘I already have an account’
Outcome
What did you expect?
The server selection screen should be shown after ~15 seconds rather than waiting for a whole 40-seconds which feels very broken.
Or better still, the server selection screen could even be shown first, before any connection test is performed on a server selected by user (this is the workflow in FluffyChat).
If a connection test must be done before a server is selected, do it on a domain known to not have been blocked anywhere instead of matrix.org.
What happened instead?
A screen says
Loading
for a whole 40 seconds whilst waiting to time out, and then the server selection screen is shown.Your phone model
iPhone SE2
Operating system version
iOS 16.3.1
Application version
Element 1.10.12
Homeserver
matrix.org
Will you send logs?
No