hevi08

facing this issue in sdk 53. any updates on this issue ? @brentvatne @lukmccall

@mikehardy could you please merge this PR ? Thanks

Use like this Either import everything from 'react-native-webrtc' or use [registerGlobals()](https://github.com/react-native-webrtc/react-native-webrtc/blob/master/Documentation/BasicUsage.md#registering-globals) ```ts import { useState } from 'react'; import { View } from 'react-native'; import { MediaStream, mediaDevices, RTCPeerConnection }...

By the way, i always import from `react-native-webrtc` directly. Because, if i use `navigator.mediaDevices.getDisplayMedia()`, vscode will tell you that, you can pass these [options](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getDisplayMedia#options) But in internally, its not taking...

In the same scenario, if I use the default UI (without passing mainComponent), it works.

After receiving the FCM, registering RNCallKeep Events and then call `RNNotificationCall.displayNotification()` on `showIncomingCallUi` callkeep event. ### Scenarios | App State (Background / Foreground / Killed) | Device State (Locked /...

> Does this bug occur both when you pass a mainComponent (custom UI) and when you don't use mainComponent? Only when `mainComponent` is passed as i mentioned in above table.