paweldomas 022954b40b fix(base/connection/reducer): clear 'connection' field ... Currently the listeners for disconnected and failed connection events are unsubscribed as soon as the connection is established, so the CONNECTION_DISCONNECTED is never triggered which would clear the 'connection' field. This commit will clear the 'connection' state on CONNECTION_WILL_CONNECT. It's needed anyway given that there's no guarantee on when and if the async disconnect operation will finish. One issue caused by the 'connection' not cleared was that CONNECTION_FAILED was not reduced correctly and the reload screen was not displayed for the following scenario: 1. Join and leave any working conference. 2. Turn off network connectivity on the device. 3. Wait for CONNECTION_FAILED. The reload screen will not be displayed, because CONNECTION_FAILED is not reduced correctly, because the old 'connection' value is still there.		2018-06-20 15:52:45 +02:00
..
actionTypes.js	CONNECTION_FAILED error as object	2017-09-24 16:51:43 -05:00
actions.native.js	ref: use getCurrentConference	2018-05-30 16:29:27 +02:00
actions.web.js	feat(deep_linking): add analytics	2018-04-26 10:11:34 +02:00
functions.js	[RN] Fix calendar alerts when case sensitive URLs are used	2018-04-04 11:21:02 +02:00
index.js	Move ConferenceUrl.inviteURL into React and redux	2017-06-01 21:04:31 -05:00
reducer.js	fix(base/connection/reducer): clear 'connection' field	2018-06-20 15:52:45 +02:00