Privacy - iOS: JitsiMeet.framework utilizes react-native-netinfo which sends HTTP requests to Google

Description

JitsiMeet.framework is used by the iOS Riot app. Using Riot it was discovered that the app sends HTTP requests to Google. This is unwanted due to privacy concerns. It seems the requests emerge from react-native-netinfo which is utilized by JitsiMeet.framework.

Current behavior

JitsiMeet.framework sends (multiple) request to clients3.google.com/generate_204 during the lifetime of the app.

Expected Behavior

JitsiMeet.framework should not loose data to Google. If react-native-netinfo provides desireable features this behaviour should be optional/configurable.

Possible Solution

Update to a version of react-native-netinfo where this behaviour is configurable.

Steps to reproduce

Install the iOS Riot app and configure it. Install the Charles proxy app. Start the Riot app. You’ll see the request to clients3.google.com in the log of Charles.

Environment details

iOS 13.4, iOS Riot app

[pixlwave]

Thought it was worth mentioning in this thread that upgrading JitsiMeetSDK to 5.0.2 in Element iOS has stopped the app from pinging Google so long as you don’t join a Jitsi call. Once that happens then we see the checks every minute even once you have left the call.t

I think the change that we ought to do here is to direct the HEAD request at the config.js file of the configured server.

Checking meet.element.io/config.js, the file is 60KB which could be considered a bit heavy for a mobile device when there isn’t much signal. Would it be feasible to expose a property so that SDK users could configure the URL themselves?

[pixlwave]

Ohhh TIL, sounds perfect 👍