Add registerGlobals() function to pollute global namespace with RTC entities

As discussed here, there are some WebRTC based JS libraries that depend on RTCPeerConnection and so on being available in global namespace.

cordova-plugin-iosrtc exposes iosrtc.registerGlobals() for that.

So the only requirement is that react-native-webrtc is loaded first, then the app calls to registerGlobals() and then the 3rd party WebRTC library can be load.

[saghul]

Thanks for bringing this up @ibc! I agree, this would be a welcome addition. I’ll try to get it done next week, if nobody beats me to it 😃

[fbruckhoff]

Hey, could use some help 😃 we’ve got a situation that looks like this:

1. A mediasoup/webRTC web app that runs in any browser.
2. An Expo-based React Native app to be installed on iOS and Android, which renders the web app (1) in a WebView.

Somehow webRTC doesn’t work on iOS when embedded in a WebView, probably due to permission issues, so I’m trying to find out how to go about making use of react-native-webrtc to solve that problem.

Right now it’s unclear to me how exactly react-native-webrtc would help in this situation. I realize we have to call registerGlobals(), but how would that trickle down properly to the WebView?