haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(base/conference): tracks not added to the conference 

If tracks are created while the conference is in the 'joining' state
they will never be added.
This commit is contained in:
paweldomas 2019-03-25 18:15:50 -05:00 committed by Saúl Ibarra Corretgé
parent 15c5a2339b
commit e839684ae9
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
react/features/base/conference/middleware.js
View File

@ -43,6 +43,7 @@ import {
import {
_addLocalTracksToConference,
forEachConference,
getCurrentConference,
_handleParticipantError,
_removeLocalTracksFromConference
} from './functions';
@ -620,13 +621,10 @@ function _setRoom({ dispatch, getState }, next, action) {
* @returns {Promise}
*/
function _syncConferenceLocalTracksWithState({ getState }, action) {
const state = getState()['features/base/conference'];
const { conference } = state;
const conference = getCurrentConference(getState);
let promise;
// XXX The conference may already be in the process of being left, that's
// why we should not add/remove local tracks to such conference.
if (conference && conference !== state.leaving) {
if (conference) {
const track = action.track.jitsiTrack;
if (action.type === TRACK_ADDED) {