jiti-meet/react
paweldomas 82f5eb894b ref(external API): emit CONFERENCE_FAILED on CONNECTION_FAILED
It seems that the external API will not send any event to let the sdk
consumer know that the conference has failed if the problem occurs at
the establishing of XMPP connection stage. That's because the config was
loaded successfully, but the conference instance does not exist yet, so
neither base/config nor base/conference will emit any failure.
2018-05-04 13:02:19 +02:00
..
features ref(external API): emit CONFERENCE_FAILED on CONNECTION_FAILED 2018-05-04 13:02:19 +02:00
.eslintrc.js feat(eslint): Enable for non react files 2017-10-16 14:36:29 -05:00
index.native.js [RN] Fix app startup from a CallKit intent 2018-02-07 10:12:10 -06:00
index.web.js fix(external_api): fire videoConferenceLeft event on unload (#2243) 2017-12-04 10:33:58 -08:00