Network Extension Beta test with Test Flight

Question

Created Jul ’22

Replies 1

Boosts 0

Participants 2

We have an App with Content Filter Network Extension. We tested our App on physical devices (iPhone and iPad) and all looked OK.

We uploaded our App build to AppStore Connect, for Test Flight. External Testers received the App, but noticed Network Extension is not triggering any function.

App downloaded from TestFlight, dint ask usual (Allow/Not Allow) Dialog box to kick start the NW Extn.

AppStore Connect Entitlements lists included NW Extn as seen in attached screenshot. Screenshot 2022-07-01 at 7.06.40 PM.png

Question is,

Is there any limitation for Apps installed via Test Flight with Network Extensions?
How to debug a Test Flight Test App or at least verify the presence of NW Extn and their logs?

Is it not safe to expect, AppStore App in production and Test Flight Installed App should behave almost same? I noticed, In the settings, the Test App installed via TestFlight is not listed on physical device, is it that TestFlight App has Sandboxed the test App and its extensions and cannot behave as normal App with its full capacity? That means NW Extn Apps cannot be tested completely via Test Flight?

Boost

Answer 1

Systems Engineer OP

Apple

Jul ’22

Accepted Answer

Is there any limitation for Apps installed via Test Flight with Network Extensions?

For iOS a Content Filter Provider Network Extension, such as NEFilterDataProvider can only be used on a supervised device unless used in-conjunction with FamilyControls / Screen Time APIs. Please see the overview section for Content Filter Providers on iOS. I suspect that is why you are not seeing it working in TestFlight. Check the logs when you try to enable the Content Filter APIs in this environment.

1