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

Jitsi preferredDomain is not taken into account #7230

Closed
yamrzou opened this issue Sep 24, 2022 · 1 comment
Closed

Jitsi preferredDomain is not taken into account #7230

yamrzou opened this issue Sep 24, 2022 · 1 comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@yamrzou
Copy link

yamrzou commented Sep 24, 2022

Steps to reproduce

I'm encountering the exact same issue as #4497 with Element Android 1.4.36.

I'm serving the following .well-known correctly under both
https://matrix.domain.tld/.well-known/matrix/client and https://domain.tld/.well-known/matrix/client:

{
  "m.homeserver": {"base_url": "https://matrix.domain.tld:443"},
  "im.vector.riot.jitsi": {"preferredDomain": "meet.domain.tld"}
}

When the call is initiated from Element Web, it uses the preferredDomain meet.domain.tld correctly. The following config is also defined in element/config.json:

"jitsi": {
    "preferred_domain": "meet.domain.tld"
},

But when the call is initiated from Element Android, it uses meet.element.io. The event source when the call is initiated from Android is as follows:

{
  "type": "im.vector.modular.widgets",
  "sender": "@user:matrix.domain.tld",
  "content": {
    "url": "https://app.element.io/jitsi.html?confId=MmUsjWstqvCXVTQLp44b9f8e#conferenceDomain=$domain&conferenceId=$conferenceId&isAudioOnly=$isAudioOnly&displayName=$matrix_display_name&avatarUrl=$matrix_avatar_url&userId=$matrix_user_id&roomId=$matrix_room_id&theme=$theme",
    "type": "jitsi",
    "data": {
      "domain": "meet.element.io",
      "conferenceId": "MmUsjWstqvCXVTQLp44b9f8e",
      "isAudioOnly": false
    },
    "creatorUserId": "@user:matrix.domain.tld",
    "id": "m.jitsi_@user:matrix.domain.tld_1664044283605",
    "name": "jitsi",
    "roomId": "!MmUsjWstqvCXVTQLpD:matrix.domain.tld",
    "eventId": "$c1hJiQNlpE6ATztH2KrIG3ydu9kmxOVBtd_p3MTTD-M"
  },
  "state_key": "m.jitsi_@user:matrix.domain.tld_1664044283605",
  "origin_server_ts": 1664044282888,
  "unsigned": {
    "age": 64
  },
  "event_id": "$c1hJiQNlpE6ATztH2KrIG3ydu9kmxOVBtd_p3MTTD-M",
  "room_id": "!MmUsjWstqvCXVTQLpD:matrix.domain.tld"
}

Outcome

What did you expect?

According to this, the call was supposed to use the custom Jitsi domain meet.domain.tld

What happened instead?

Call was setup using meet.element.io

Your phone model

Pixel 5

Operating system version

Android 12

Application version and app store

Element 1.4.36

Homeserver

Synapse 1.67.0+bullseye1

Will you send logs?

No

Are you willing to provide a PR?

Yes

@yamrzou yamrzou added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Sep 24, 2022
@RiotRobot RiotRobot added this to Incoming in Issue triage Sep 24, 2022
@yamrzou
Copy link
Author

yamrzou commented Sep 24, 2022

Solved after reinstalling the app, probably a cache issue.

@yamrzou yamrzou closed this as completed Sep 24, 2022
Issue triage automation moved this from Incoming to Closed Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
No open projects
Development

No branches or pull requests

1 participant