.well-known error doesn't clear when trying localpart login instead

[turt2live]

1. Enter your full mxid
2. Get error
3. Enter your localpart
4. Stuck in error

May be fixed by matrix-org/matrix-react-sdk#2327

[lampholder]

It doesn't look like this has been fixed (the experience is still as described on /develop today at least)

[dkasak]

Can this please get bumped up in priority? This isn't minor, I've had several users unable to log in because of this. Even worse, after a few hours of back and forth with a user trying to debug this, it just started working spontaneously (probably because they manage to reset the state somehow), making this very difficult to debug.

EDIT: Also, it seems the error you now get with this issue is the one from #7925 ("Invalid homeserver discovery response").

[jryans]

@dkasak, do you agree that this particular issue no longer reproduces on https://riot.im/develop? At least, I can't seem to reproduce it here from the original steps on develop. When I change to just a localpart, the discovery error is cleared.

(I agree we should address #7925 as well, but let's leave that for the other issue.)

[dkasak]

I confirm that I can't reproduce this on the develop version of Riot.

There's still a rough edge left, though: following the original steps, at step 4 I am no longer stuck at the error, but I have to click on "Sign in" twice to sign in (the first click is ignored).

(And yes, I only mentioned #7925 for cross-referencing since it took me a while to land on this issue.)

[jryans]

Okay, great to hear this is fixed at least. Probably by matrix-org/matrix-react-sdk#2539 or similar.

There's still a rough edge left, though: following the original steps, at step 4 I am no longer stuck at the error, but I have to click on "Sign in" twice to sign in (the first click is ignored).

I wasn't able to reproduce this part, so I'd suggest a new issue with more detail about exactly what you are entering and clicking each step of the way.