-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
If inviting a user fails, user is shown a cryptic 'Failure to create room' error. #4062
Comments
This is expected, the only situation in which you should expect your intention before being a PWLU to be carried forward is when joining |
it's still a very cryptic error though... |
Agreed, but this is quite orthogonal to ILAG and could be improved for invites in general. |
Can we categorise this as "Failed invites should give better feedback than 'failure to create room' error", or something similar? |
Modifying the title, classifying as a bug and booting out of ILAG. |
P2 minor because (if I understand this correctly) this will only affect people who:
|
It is an awful experience for people who are running riot on a new non-fed HS though.
…--
Matthew Hodgson
Matrix.org
On 1 Jun 2017, at 10:24, Tom Lant ***@***.***> wrote:
P2 minor because (if I understand this correctly) this will only affect people who:
use a riot instance they don't host (and hence can't reconfigure the welcomeUserId setting in config.json)
to connect to a home server that can't federate with matrix.org
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This is still present in the redesign branch fwiw. Edit: And in some ways it is worse in the redesign, after registering, the app hangs with a gray screen and static spinner for upwards of a minute or so, before throwing the error message. Most of my test users just refreshed the page, other thought it was broken. |
|
I was testing ILAG on my local HS, which is not federated. It tried to invite riot-bot which failed with a 502 (not unreasonably), bubbling up a "Failure to create room" error. However, it then ditched me and didn't let me complete the flow to actually fill in the 'start chat' or 'create room' dialogs.
The text was updated successfully, but these errors were encountered: