From 675eea7b99095b9971a24bc403d48521b58bca6e Mon Sep 17 00:00:00 2001
From: paweldomas <pawel.domas@jitsi.org>
Date: Wed, 20 Jun 2018 09:44:56 +0200
Subject: [PATCH] fix(base/conference): do not execute leave conference on web

On web CONFERENCE_FAILED handlers are not setting the 'recoverable'
flag thus any middleware which rely on those should not execute on web.
---
 react/features/base/conference/middleware.js | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/react/features/base/conference/middleware.js b/react/features/base/conference/middleware.js
index c6006c44f..60e9dfed1 100644
--- a/react/features/base/conference/middleware.js
+++ b/react/features/base/conference/middleware.js
@@ -108,6 +108,13 @@ MiddlewareRegistry.register(store => next => action => {
 function _conferenceFailed(store, next, action) {
     const result = next(action);
 
+    // FIXME: Workaround for the web version. Currently, the creation of the
+    // conference is handled by /conference.js and appropriate failure handlers
+    // are set there.
+    if (typeof APP !== 'undefined') {
+        return result;
+    }
+
     // XXX After next(action), it is clear whether the error is recoverable.
     const { conference, error } = action;