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

feat(base/connection): log leave failure reason 

Because there are multiple reasons on why a conference.leave() may fail
it's helpful to know if and why it happened.
This commit is contained in:
paweldomas 2018-05-17 09:53:51 -05:00 committed by Lyubo Marinov
parent 75c7cfd9e1
commit 7704809c4c
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
react/features/base/connection/actions.native.js
View File

@ -15,6 +15,8 @@ import {
SET_LOCATION_URL SET_LOCATION_URL
} from './actionTypes'; } from './actionTypes';
const logger = require('jitsi-meet-logger').getLogger(__filename);
/** /**
* The error structure passed to the {@link connectionFailed} action. * The error structure passed to the {@link connectionFailed} action.
* *
@ -322,7 +324,11 @@ export function disconnect() {
promise promise
= conference_.leave() = conference_.leave()
.catch(() => { .catch(error => {
logger.warn(
'JitsiConference.leave() rejected with: ',
error);
// The library lib-jitsi-meet failed to make the // The library lib-jitsi-meet failed to make the
// JitsiConference leave. Which may be because // JitsiConference leave. Which may be because
// JitsiConference thinks it has already left. // JitsiConference thinks it has already left.