3 Commits (3cb0df579ca5b8615dfba1b8b901bca1c8ca9ac4)

Author	SHA1	Message	Date
Saúl Ibarra Corretgé	d3d442e4d2	fix(rn,polyfills) simplify WebRTC polyfills ... Use the polyfiller provided by react-native-webrtc. Drop the permissions API polyfill since we no longer use it in the app and lib-jitsi-meet already works without it.	3 years ago
Bogdan Duduman	48db099134	feat: include sort members eslint changes	3 years ago
Saúl Ibarra Corretgé	caabdadf19	rn,polyfills: refactor all mobile polyfills ... Move all polyfills to a standalone feature, which gets imported before anything else in the mobile entrypoint. This guarantees that any further import sees the polyfilled environment.	6 years ago
Saúl Ibarra Corretgé	a327a5d804	[RN] Drop the react-native-permissions dependency ... It causes false positives when submitting the app to the Store. Use the new permissions API in react-native-webrtc instead.	7 years ago
Saúl Ibarra Corretgé	1354731fc5	[RN] Update WebRTC polyfills	7 years ago
Lyubo Marinov	e622829c1c	[RN] Promised-base RTCPeerConnection API ... Recent changes in lib-jitsi-meet probably led to (1) our RTCPeerConnection customizations on react-native not being used which is a problem because we need them for at least NAT64 on iOS in order to pass the review in Apple's App Store and (2) unexpected exceptions inside react-native-webrtc. The Promise-based WebRTC API should be merged from react-native-webrtc's upstream but I don't want to do it right now because last time we got multiple bugs in addition.	8 years ago
paweldomas	16d9ef5f1c	[RN] export RTCIceCandidate ... Required for P2P.	9 years ago
Lyubomir Marinov	9f332ffcec	[iOS] Synthesize IPv6 addresses	9 years ago
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 ... As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at 2f23d98424 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	9 years ago