jiti-meet/react/features/mobile
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
..
audio-mode [RN] Translate AudioRoutePickerDialog 2017-11-20 07:54:05 -06:00
background [RN] Make full-screen more resilient on Android (Coding style: consistency) 2018-02-14 12:28:22 -06:00
callkit Codying style: naming, formatting, comments 2018-05-03 18:04:59 -05:00
external-api ref(external API): emit CONFERENCE_FAILED on CONNECTION_FAILED 2018-05-04 13:02:19 +02:00
full-screen [RN] Make full-screen more resilient on Android (Coding style: consistency) 2018-02-14 12:28:22 -06:00
image-cache [RN] Fix documentation comments 2017-10-01 01:35:19 -05:00
network-activity [RN] Make full-screen more resilient on Android (Coding style: consistency) 2018-02-14 12:28:22 -06:00
permissions Reorganize calendar access request flow 2018-03-23 07:53:36 +01:00
picture-in-picture ref(PiP/actions): remove 'is ok to enter PiP' check 2018-05-02 17:06:24 +02:00
proximity [RN] base/media is intent, base/tracks is reality 2017-08-04 16:07:48 -05:00
wake-lock [RN] Add audio only mode for conferences 2017-04-05 15:07:34 -05:00