diff options
author | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2023-02-17 10:41:02 +0100 |
---|---|---|
committer | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2023-02-20 15:12:05 +0100 |
commit | 44e36fe9b2454f87914e139dcd9ec3d9e743cab5 (patch) | |
tree | 6b7dcd56c3cf5bbe144c5fbfcafa7db7bfee902f /src | |
parent | c225b2fb04bcea044fb941c906295cf14b5604e7 (diff) |
Do not try to fetch participant data from Nextcloud when recording
The recording participant does not have a Nextcloud session, so it can
not fetch the participant data. Nevertheless, this should be a transient
situation (for example, if a new participant was found but that
participant did not send yet the initial state with the name) and
eventually all the needed data for the call view should be available
from the signaling data.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Diffstat (limited to 'src')
-rw-r--r-- | src/components/CallView/CallView.vue | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/src/components/CallView/CallView.vue b/src/components/CallView/CallView.vue index c36e431f5..16f470b69 100644 --- a/src/components/CallView/CallView.vue +++ b/src/components/CallView/CallView.vue @@ -635,6 +635,14 @@ export default { }, debounceFetchPeers: debounce(async function() { + // The recording participant does not have a Nextcloud session, so + // it can not fetch the peers. This should not be a problem, as all + // the needed data for the recording should be (eventually) + // available in the signaling data. + if (this.isRecording) { + return + } + const token = this.token try { const response = await fetchPeers(token) |