NEFilterDataProvider development-signed bypass no longer working on iOS 26.4.2 — regression or intentional?

Question

Colin_newbie OP

Created 5d

Replies 1

Boosts 0

Participants 2

Hi,

Has the get-task-allow development bypass for NEFilterDataProvider been intentionally removed or changed in iOS 26?

Previous DTS guidance in thread/31109 confirmed this bypass existed. I note that WWDC 2025 Session 234 states "iOS system-wide content filter is supported on supervised devices only" without mentioning it.

My production deployment is supervised MDM devices — I am purely asking about the development testing path, which is not working for me on iOS 26.4.2. All I get is NEConfigurationErrorDomain Code=10 "permission denied" before my app code even runs.

Thank you!

Boost

Answer 1

DTS Engineer OP

Apple

3d

AFAIK there’s been no change of policy on this front.

That WWDC session, and for that matter TN3134, don’t discuss this debugging affordance because they’re focused on deployment, not development.

All I get is NEConfigurationErrorDomain Code=10 "permission denied" before my app code even runs.

I don’t understand this comment. This affordance affects your ability to save a configuration. That is, with this affordance your container app can successfully save a configuration using NEFilterManager.saveToPreferences() under circumstances where it would not normally be allowed to do that. So I’m struggling to see how you could get into this situation “before my app code even runs”. Please clarify.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0