https://github.com/react-native-community/releases/blob/master/CHANGELOG.md#v0598

It's possible a CallKit event arrives when the React Bridge has been torn down
and there is an assert that checks this. In order to avoid a crash, just skip
the event.

It was extracted from the RN core to a community maintained package.

New M69 build with Metal crash fixes.

Time has come. We need to enable bitcode. It's optional for iOS targets, but
mandatory for the entire project if there is a watchOS target. Since we have a
watchOS target, it's time to enable it.

Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>

- handle some weird bug
(https://github.com/firebase/firebase-ios-sdk/issues/233)
- use a common function to extract the URL off a dynamic link

Replace the Swift array with an Objective-C one, since it's going to store
Objective-C objects and not Swift objects (or Swift objects which inherit from
NSObject, which is equivalent).

This avoids the need for JMCallKitEventListenerWrapper entirely, since an
NSArray can store NSObjectProtocol objects, unlike a Swift array, which prompted
the creation of the wrapper in the first place.

The SDK will now search for an asset called "CallKitIcon" on the main bundle,
and fallback to a built-in asset it it's not there, allowing SDK users to
customize it by just adding asset with that name.

When CallKit is enabled / disabled, a new CXProvider must be created in order to
not confuse CallKit (it misbehaves otherwise).

Ever since we switched to handling track events instead of mute actions this has
been dead code. It was also added in the wrong place, since it's responsibility
of the JS code to solve the ping-pong problem.

While that option should default to true, let's be explicit about it.

It now lives here: https://github.com/jitsi/jitsi-meet-sdk-samples

- Xcode 10.2 + Swift 5
- Latest SDK API
- Fix warnings

Fixes a crash on some old Android devices.

https://docs.fastlane.tools/codesigning/xcode-project/#xcode-9-and-up

It complicates automated builds.

Signing wouldn't work, disabling it and enabling it again created these changes.
Oh well!

NSURLConnection sendSynchronousRequest is deprecated since iOS 9. Replace the
method by whjat's currently on RN master, which implements a modern alternative.

This new version comes with an updated JSC runtime, so we no longer need to
depend on the updated version ourselves.

The app should always provide them.

Consolidate all failure cases into a single one: CONFERENCE_TERMINATED. If the
conference ended gracefully no error indicator will be present, otherwise there
will be.

Since the SDK may be embedded with other apps, we need to recognize our custom
URL scheme and universal links in order to tell the user if we will process the
request or not.

Make them configurable with sane defaults.