DNS Proxy Provider remains active after app uninstall | iOS

Hi,

I've encountered a strange behavior in the DNS Proxy Provider extension. Our app implements both DNS Proxy Provider and Content Filter Providers extensions, configured via MDM.

When the app is uninstalled, the behavior of the providers differs:

• For Content Filter Providers (both Filter Control and Filter Data Providers), the providers stop as expected with the stop reason:

/** @const NEProviderStopReasonProviderDisabled The provider was disabled. */
case providerDisabled = 5

• However, for the DNS Proxy Provider, the provider remains in the "Running" state, even though there is no app available to match the provider's bundle ID in the uploaded configuration profile.

When the app is reinstalled:

• The Content Filter Providers start as expected.
• The DNS Proxy Provider stops with the stop reason:

/** @const NEProviderStopReasonAppUpdate The NEProvider is being updated */
@available(iOS 13.0, *)
case appUpdate = 16

At this point, the DNS Proxy Provider remains in an 'Invalid' state. Reinstalling the app a second time seems to resolve the issue, with both the DNS Proxy Provider and Content Filter Providers starting as expected.

This issue seems to occur only if some time has passed after the DNS Proxy Provider entered the 'Running' state. It appears as though the system retains a stale configuration for the DNS Proxy Provider, even after the app has been removed.

Steps to reproduce:

1. Install the app and configure both DNS Proxy Provider and Content Filter Providers using MDM.
2. Uninstall the app.

• Content Filter Providers are stopped as expected (NEProviderStopReason.providerDisabled = 5).
• DNS Proxy Provider remains in the 'Running' state.

1. Reinstall the app.

• Content Filter Providers start as expected.
• DNS Proxy Provider stops with NEProviderStopReason.appUpdate (16) and remains 'Invalid'.

1. Reinstall the app again.

• DNS Proxy Provider now starts as expected.

This behavior raises concerns about how the system manages the lifecycle of DNS Proxy Provider, because DNS Proxy Provider is matched with provider bundle id in .mobileconfig file.

Has anyone else experienced this issue? Any suggestions on how to address or debug this behavior would be highly appreciated.

Thank you!