Used for building and deploying builds to TestFlight and the App Store.

Read it from the GoogleService-Info.plist file and apply it into Info.plist.

No caps are allowed, so this would trigger a rejection when uploading to
TestFlight.

Co-authored-by: DimaG <dgeorgiev06@gmail.com>

This is mostly implemented in the app, with the needed support in the SDK. Since
the app needs to donate intents and deal with creating NSUserActivity objects it
doesn't feel right to do this in a library. Instead, we donate the intents from
the app, but the SDK is ready to extract conference URLs from any intent which
was registered as a conference activity.

This also opens the door for eventually adding Handoff support.

Share the code for extracting the URL for conference from a NSUserActivity.

This is done at the app level, not the SDK.

Currently 2 Firebase services are used:

  - Crashlytics
  - Dynamic Links

They are enabled in tandem, if the appropriate Google services file
(GoogleService-Info.plist on iOS or google-services.json on Android) is found.

Each service needs to be individually enabled in the Firebase console.

Mention the availability of CocoaPods.

Also update the bundle ID since we don't release with that anyway.

Bumping React to 16.6.3 is a requirement for this update.

It doesn't add any value, by default HTTP is not supported unless an exception
is added, plus it doesn't work in browsers at all.

WebRTC no longer actively fixes iOS 9 issues.

Xcode 10 introduced a new build system. Alas, it breaks a number of important
flows, such as creating an archive for the framework (ie SDK) target.

In order to "fix" this, switch back to the former (Xcode 9) build system for the
time being.

The upstream package has been unmaintained for 2 years now, and making the litle
changes needed as React Native needs them is getting old. The actual
funcionality is a couple of one-liners plus tons of boliterplate, which gets
reduced by quite a bit if we just embed it. So here it goes.

When a native iOS module implements `constantsToExport` it must define
`requiresMainQueueSetup`. In this case we don't do any UI stuff so it doesn't
need to be initialized in the main thread.

Make sure both methods offer the same behavior and mark the old one as
deprecated so SDK users get a warning.

This reduces 'xcodebuild' verbosity and fixed problem with exceeding 4MB
of logs size imposed by Travis CI.

It causes false positives when submitting the app to the Store. Use the new
permissions API in react-native-webrtc instead.

App Store Connect reported the following issues in (and rejected the binary
of) Jitsi Meet 1.18.x:

NSBluetoothPeripheralUsageDescription
NSAppleMusicUsageDescription
NSMotionUsageDescription
NSSpeechRecognitionUsageDescription

Starting spring 2019, all apps submitted to the App Store that access user
data will be required to include a purpose string for the following:

NSLocationAlwaysUsageDescription
NSLocationWhenInUseUsageDescription

PR https://github.com/wmcmahan/react-native-calendar-events/pull/186 has
been merged upstream.

Includes a fix for not running expensive operations on the main thread.

Use react-native-fastimage, which uses 2 full-native image impleentations using
well known and mature (native) libraries.

This gets us rid of 2 libraries which were observerd as a source of bugs and
created trouble with dependencies: react-native-fetch-blob and
react-native-img-cache. They are also no longer well maintained.

With the fastimage lib Travis complains about:

CocoaPods could not find compatible versions for pod "SDWebImage/Core"

There is no reason for them to run on the main thread, it's safe to call
AVFoundation functions on threads other than the main thread.

The previous code made an incorrect claim about the thread in which the audio
route change notification selector is called: it's called on a secondary thread:
https://developer.apple.com/documentation/avfoundation/avaudiosessionroutechangenotification

It will only be requested if a user joins a meeting or flips the switch from
video to audio and back, but never as the first thing when the welcome page is
mounted.