Skip to content
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

Attempting to join a Jitsi video call fails when you have no display name set #25510

Closed
hanthor opened this issue Jun 1, 2023 · 13 comments · Fixed by matrix-org/matrix-react-sdk#11319

Comments

@hanthor
Copy link

hanthor commented Jun 1, 2023

Steps to reproduce

  1. Where are you starting? What can you see?
    in a regular room from a user account with a blank display name

  2. What do you click?
    The video call button

5.Join the video call, it never joins

Outcome

What did you expect?

Be able to join a Jitsi call, even from a nameless user

What happened instead?

It gets stuck loading

Operating system

Windows, MacOS

Browser information

chrome 113

URL for webapp

app.element.io

Application version

1.11.26

Homeserver

1.80

Will you send logs?

No

@hanthor hanthor changed the title Attempting to join a Jitsi video call fails when you have o display name set Attempting to join a Jitsi video call fails when you have no display name set Jun 1, 2023
@weeman1337
Copy link
Contributor

@hanthor Unfortunately I cannot reproduce your issue. Please update your issue with more information. If we don’t hear back from you in a week, we will close the issue as we need to be able to reproduce it before we can fix it.

I have tested with a user with a blank display name. Jitsi falls back to the MXID in this case for me. I would also recommend to update to a more recent client version of Element Web. app.element.io currently ships 1.11.31 . Did you use another environment?

@t3chguy
Copy link
Member

t3chguy commented Jul 13, 2023

Closing due to no response & cannot repro

@t3chguy t3chguy closed this as completed Jul 13, 2023
@hanthor
Copy link
Author

hanthor commented Jul 18, 2023

I'm able to re-pro on bluk created users with no display name set.

console-export-2023-7-18_13-44-55.txt

Not much in the way of output to console. I have a screen recording, but I have no idea how to increase the logging to get something helpful

@hanthor hanthor reopened this Jul 18, 2023
@t3chguy
Copy link
Member

t3chguy commented Jul 19, 2023

Cannot reproduce either. Can you share the screen recording?

@hanthor
Copy link
Author

hanthor commented Jul 19, 2023

@hanthor
Copy link
Author

hanthor commented Jul 19, 2023

I can give access to the instance too if you want

@t3chguy
Copy link
Member

t3chguy commented Jul 19, 2023

@hanthor if it can't be reproduced on a public server + public instance its unlikely to be dealt with by the team, I'd suggest trying to reproduce it there

@hanthor
Copy link
Author

hanthor commented Jul 19, 2023

Well, it's affecting pain customers on ESS. The only way I know how to create it is using the both user creation with synapse admin.

I could maybe set up an ENS cloud host, but I don't think there's a way to reproduce it on a public public server

@hanthor
Copy link
Author

hanthor commented Jul 19, 2023

Actually scratch that I probably can't reproduce it on EMS Cloud host since it uses meet.element.io for jitsi

@hanthor
Copy link
Author

hanthor commented Jul 21, 2023

I can give anyone access to the server with a login so that you can repro the issue

@daniellekirkwood
Copy link
Contributor

Stepping in -- I've been given more context to this issue and we'll need to find the right place for it to slot into our backlog somewhere. I will discuss this with @Johennes this afternoon and we'll discuss online and in Element in the following days :)

Please do not close this issue until it's resolved for @hanthor !

@weeman1337
Copy link
Contributor

I will take care of it, together with @hanthor

@weeman1337
Copy link
Contributor

weeman1337 commented Jul 25, 2023

The problem here is that an empty profile (neither displayname nor avatar) leads to a 404. The OwnProfileStore will never be ready → widget won't start.

Issue created in Synapse: matrix-org/synapse#16000 . It should not 404 if only the displayname is empty.

Going to implement a handling for 404s in Client::getProfileInfo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants