element-hq / element-hq/element-ios
A videoconference that has been completed for everyone always appears as “in progress” in the mobile application.
- Dominant language
- Swift
- Stars
- 1.8k
- Forks
- 544
- PR merge metrics
- PR metrics pending
Description
### Steps to reproduce
If a videoconference is initiated from a lounge with at least 3 people, and a user joins the videoconference from the Element mobile application, if another user ends the videoconference for everyone, the videoconference still appears in progress in the mobile application.
To be more precise, if a user joins a videoconference, from the Element mobile application, in a lounge with at least 3 participants, and then another initiator of the meeting ends the videoconference, the Element mobile application interface indicates that the meeting is still in progress.
For example, if the user is the meeting initiator, the “End meeting for everyone” banner always appears:

In all cases, the re-join button appears as if the meeting had not yet ended:

This problem also appears when reloading the mobile application from the phone. However, restarting the smartphone refreshes the interface.
### Outcome
#### What did you expect?
- When the videoconference initiator ends the meeting for all, the mobile application of a user joining the videoconference in the lounge should update to no longer indicate that the meeting is in progress.
#### What happened instead?
When a user ends a meeting, it is still displayed in progress in the Element mobile application.
### Your phone model
Iphone 14
### Operating system version
_No response_
### Application version
_No response_
### Homeserver
_No response_
### Will you send logs?
Yes
Contributor guide
Research direction
Start by reproducing the lounge videoconference with at least three participants in the Element mobile application, ending it for everyone from another initiator, then reloading the app. Done means the in-progress banner and re-join button disappear after the meeting ends; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100