Network Extension URL Filter registration pending review for more than a month

Hello,

I am writing about a Network Extension URL Filter configuration submitted through the Identity & Trust section of the CloudKit Console on 5 September 2026

Status shown: In Review / Waiting for Approval Last Modified: 5 September 2026 (unchanged since submission)

It has now been 37 days with no response — no approval, no rejection, and no request for changes. The PIR server , Privacy Pass issuer and HTTP/2 OHTTP gateway have been live and serving since the day of submission, configured per the Onboarding.md guidance in Apple's PIR service example, including the apple-url-filter DNS TXT record on the service URL and the url-filter-test validation entry.

Could anyone please let me know:

  1. Whether this configuration is actually in a review queue, and the expected timeframe;
  2. Whether anything further is required from our side — if so, we will act on it the same day.

The URL filter is a core protection feature of our app, which is currently in App Store review; the feature stays disabled for users until this registration is approved, so the delay is holding up what we can ship.

Thank you for your help.

Answered by DTS Engineer in 909181022

Hmmmm, I think that things might’ve ‘crossed in the mail’. What does your CloudKit Console status show now?

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

Accepted Answer

Hmmmm, I think that things might’ve ‘crossed in the mail’. What does your CloudKit Console status show now?

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

Hi Thanks for your response its approved Thank you very much !

@DTS Engineer Thanks for your reply and support. Now that the configuration is approved. What are the next steps How long does it usually take for the service to be provisioned ?

kind regards

What are the next steps

Apple needs to run through the onboarding process. Unless there’s some sort of problem, there’s nothing for you to do until it completes.

How long does it usually take for the service to be provisioned ?

There’s no official guidance.

If you rummage around on the forums you’ll find experience reports from other developers. My only caution on that front is to that it took a while for this process to get going properly, so it’s best to focus on recent experience and discount reports from back when URL filters were first introduced.

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

NEURLFilter: distributed build never requests Privacy Pass tokens; /config arrives without a token

Our Identity & Trust configuration (1b152c9b…) shows "Successfully Onboarded". The app is net.codesire.sireshield, and the filter extension is net.codesire.sireshield.URLFilterExtension. We are testing a TestFlight build on iOS 26, configured like this:

pirServerURL https://pir.sireshield.io
pirPrivacyPassIssuerURL https://issuer.sireshield.io
pirAuthenticationToken: the issuer's user token

These are the hostnames registered on the form. The service is based on apple/pir-service-example.

When our server requires Privacy Pass, every request from three devices is POST /config without a token. The server refuses them with 401, and the filter shows "Invalid" in Settings. In seven days of logs, no device has ever called the issuer (/token-key-for-user-token or /issue). The issuer answers token-key-for-user-token correctly when we call it with the same user token (HTTP 200).

With token checks disabled on the server, the same build works end to end: the filter is Running, url-filter-test is blocked and /queries are answered.

Example refused requests (19 Nov 2026, UTC): 14:18:17, 14:18:50, 14:19:01, 14:20:41. Request ids: f205dee8f1a86d0f4c792cfa61f68004, …68005, …6800b, …6801d.

Questions:

Is token issuance expected to work for TestFlight builds once onboarding shows "Onboarded", or is there another enablement step?
Should token requests to the issuer go through the relay, and to which of our registered gateway URLs?
Is there anything in the configuration above that would stop the system from contacting the issuer?

A sysdiagnose from an affected device is available on request.