If action is null (observed on some old devices) we'll get an exception.
Reversing the check fixes it since Actions.XXX is statically defined.

We are downloading code off the Internet and executing it on the user's device,
so run it sandboxed to avoid potential bad actors.

Since it's impossible to eval() safely in JS and React Native doesn't offer
something akin to Node's vm module, here we are rolling our own.

On Android it uses the Duktape JavaScript engine and on iOS the builtin
JavaScriptCore engine. The extra JS engine is *only* used for evaluating the
downloaded code and returning a JSON string which is then passed back to RN.

None of them work on mobile.

- use AbortController for setting the fetch timeout
- use async / await syntax for clarify
- set the default timeout to 5s (previously non-existent, aka 0)
- add ability to load but not evaluate a script

They never worked on mobile and pose an impediment for makinf config.js more
future proof. Specially if we want to move to a non-executable form of
configuration.

For now all keys are whitelisted.

- simplify initialization procedure
- set user display name as the Etherpad name\
- use SharedDocumentButton

See: https://github.com/jitsi/jitsi-meet/issues/4720

This adds an option to disable video autoplay that will be used mostly with maleus (our selenium-based load testing tool for testing the new bridge). Disabling video rendering lowers the resource utilisation of the selenium nodes.

It's available on both Xcode 10 and 11.

* Adds notifications for who stop/start recording/live streaming.

* Updates to latest lib-jitsi-meet.

defined in RFC7050 instead of 'nat64.jitsi.net' as suggested by
Jonathan Lennox.

Fixes iOS crashes when restarting the AudioUnit in case of interruption.

It crashes like hell. See:
https://bugs.chromium.org/p/webrtc/issues/detail?id=11002

Adds option to limit number of outgoing calls per user.

Avoid Android crashes.

Uses sendBeacon to send xmpp presence unavailable on unloading the window(leaving the conference).

It was referencing LJM from a PR branch instead of the master.

If the Activity is put into the background before the ReactContext is created we
get an NPE here. While the window might be short, it's thechnically possible to
hit this, as our Crashlytics reports show.