Appearance of a banner to end the meeting for everyone, even when the user account did not initiate the meeting. After it has appeared, the “End meeting for everyone” banner has no effect. #8943
Labels
T-Defect
Something isn't working: bugs, crashes, hangs and other reported problems
Steps to reproduce
From the Element mobile application, when joining a videoconference initiated from a room where 3 or more people are present, and the user account, from the mobile, has the “Moderator” or “Administrator” role, a banner allowing the meeting to be terminated for all appears even if the user connected to the phone was not the initiator of the meeting. Conversely, this banner does not appear when the user has default rights in the room.
Furthermore, once the banner appears, if you try to end the meeting from this banner, it will have no effect, even if the user who wants to end the meeting from the cell phone is the initiator of the meeting.
To be more precise, when a user joins a videoconference from the Element mobile application, having the “moderator” or “administrator” role in the :
A banner appears, allowing you to end the meeting for everyone, even if the user did not initiate the meeting (screenshot on the IOS application, but the problem also occurs on the android application):
When the user wishes to end the meeting for all with this banner, it has no effect on the meeting in progress (in the case of the IOS application, it displays the error message shown in the previous screenshot).
However, if the user has “default” rights in the living room, this banner does not appear on the mobile application.
Outcome
What did you expect?
What happened instead?
Even when the user is not the initiator of the videoconference, the “End meeting” banner is displayed.
The “End meeting” banner has no effect.
Your phone model
Samsung Galaxy A35
Operating system version
Android 14
Application version and app store
No response
Homeserver
No response
Will you send logs?
Yes
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: