It has to be an application context.

Implements: https://developer.mozilla.org/en-US/docs/Web/API/Performance
Ref: https://github.com/oblador/react-native-performance

YOLO.

Amplitude has gone back to having a separate package for RN, so switch to it.

Allows for overriding any (overridable, of course) config option.

* feat(share-video) Allow sharing direct video links (mp4 etc) on mobile

* fix linting

* code review

- Fixed react native community slider to work on both android and ios
- Removed InviteButton from native menus
- Fixed buttons spacing in native OverflowMenu
- Participant context menu details are shown only for remote participants

Check whether context is that of an Activity before launching the Jitsi Conference Activity. If context is not an activity context, apply flag FLAG_ACTIVITY_NEW_TASK to the Jitsi Activity Intent to ensure activity can launch without error.

This scenario would manifest when a user attempts to launch the Jitsi Actvity from a Widget... for example.

https://developer.android.com/about/versions/pie/android-9.0-changes-all#fant-required

feat(external_api) exposes more events from JS to native and adds the ability to send actions from native to JS.

This may happen due to API misuse, but also in complex applications where
activity lifetimes are not straightforward.

The amplitude-js library gained React Native support so there is no need to keep
separate implementations.

Ref:
https://developer.android.com/reference/android/app/Activity#setVolumeControlStream(int)

Looks like audio devices must be re-set after focus was lost and regained.
Otherwise some devices (tested on a Samsung Galaxy S9) are in a weird state
where the second microphone is not used when speakerphone is on.

Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>
Co-authored-by: zycwind <391321232@qq.com>

JSC wasn't the cause for the crash we were hunting after all. RN doesn't set
HErmes as the default, neither does Expo, so the jury is still out on Hermes,
and it looks like JSC is still the safest bet.

In addition, the way Hermes is packaged (as a standalone AARs, instead of a
local "Maven repo") complicates the SDK build and can make the resulting build
bloated.

The RN Permissions module calls this in a non-UI thread. What we observe is a
crash in ViewGroup.dispatchCancelPendingInputEvents, which is called on the
calling (ie, non-UI) thread. This doesn't look very safe, so try to avoid a
crash by pretending the permission was denied.

Android < 23 is currently less than 3% for us so let's try to lower the
maintenance burden. Users can still download an older version no problem.

Despite running Android 8.1, they don't support Picture-in-Picture.

Rebase our patches (in PR) on top of latest master.

Sshould fix a crash when requesting permisssions.

- No need to handle the activity result in the fragment, since we already do in
  the Activity
- Automagically ddispose the view when destroyed

Co-authored-by: Titus-Andrei Moldovan <moldovan.titus@gmail.com>

In the Android SDK, the setServerURL option is erroneously
ignored. The meeting's serverURL always defaults to
https://meet.jit.si because the serverURL is not parceled.

We see tons of crashes on Samsung and Huawei devices. It's really not worth the
headache anymore.

Do so on the main thread at startup and pass it along.

They just keep crashing.

In 49e3b03885 we turned on SW encoders / decoders
on account of some devices having broken HW *encoders* and also our desire for
using simulcast.

Well, the astute reader may have noticed that only *encoding* was mentioned.
Indeed, we should be able to keep using the HW decoder just fine.

Use ANDROID_ID:
https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID

This shouldn't be needed, as ConnectionService should take care of it, but we
suspect some devices don't do it since we got reports of people not hearing
users, and the problem went away when CS was disabled.