Got it, thanks for clarifying — that makes sense. Is there anything needed from my side for the onboarding step, or is it now entirely on Apple's end? And do you have any rough sense of timeframe (days, weeks, months) I should plan around, even approximate? Just trying to figure out whether to keep waiting or look at alternatives in the meantime.

Thanks for looking into it, @DTS Engineer Quinn! Just to clarify though — this isn't a new PIR onboarding in progress. The configuration (ID 9f3cbff8-63de-4c69-bf68-c19cd1c5d842) was already fully approved back on Aug 5, so there's no review pending on the PIR server itself. The actual issue is that it's attached to the wrong Apple Developer Team (ex personnel acc Romain Scotto : S5VDH23BBZ instead of the organisation acc SCOTTO : KRKJ76BC7W), and the portal blocks any attempt to fix that with "A configuration with the same PIR Server Domain already exists." So there's nothing to wait out — it's purely a matter of reassigning the existing approved config to the correct team. Does that change things on your end?

Hi @DTS Engineer Quinn — just following up. It's been about two weeks now since you opened this, and past the ~1 week check-in you'd mentioned. I haven't seen any status change on FB24607828 in Feedback Assistant yet. Any update on where things stand? Thanks again for your help.

Filed as FB24607828. Thanks again for the help, Quinn!

Thanks so much for taking the time to look into this, Quinn — really appreciate it. One thing that might be useful context for whatever direction you're investigating: the configuration itself (bundle ID, PIR server, all endpoints) is already fully validated and correct — the only thing wrong is which Team ID it's attached to. So if there's any way to simply re-attach/reassign it rather than routing it through a brand new full review (which took about 7-8 weeks last time), that would save a lot of time for what's really just a one-field correction. Totally understand if that's not how things work on your end though — just flagging it in case it's helpful. Thanks again for the help!

Quick bump — it's been a couple of days with no response yet, and this is quite time-sensitive on my end. Is there anyone from Apple DTS who could help with this, or who might have the right internal contact to get an approved configuration reassigned between Team IDs? Also — genuine question, since I'm not familiar with the process: if I open a paid Technical Support Incident (TSI) for this, is that actually something DTS engineers can act on for an account/entitlement-transfer issue like this one? Or would it likely get bounced as "out of scope" since it's more of an account administration matter than a code-level technical question? I'd rather not spend one of my two free incidents on this if it's not the right tool for the job. Any pointer — even just "this isn't something the forum/DTS can fix, go through X instead" — would genuinely help at this point. Thanks again for any help.

Hi everyone, I've been following this thread closely — it's been extremely helpful for getting NEURLFilterManager working. I'm now facing the pirSkipRegistration = NO blocker. My setup: Filter extension activates and deactivates correctly (cycle works end-to-end on iOS 26.5) configurationInvalid is resolved (trailing slash fix + correct usecase name) PIR server deployed at https://dropbet-pir.fly.dev/ (Swift PIR Service, 4 shards, ~208K domains) Usecase: com.dropbet.DropBet.url.filtering Entitlement url-filter-provider confirmed on both app and extension targets Privacy Pass disabled server-side for dev testing The filter is active but never sends /queries to my server — because pirSkipRegistration = NO, iOS requires Privacy Pass via Apple's OHTTP relay before forwarding any PIR queries. My question: what is the exact process to register a PIR server with Apple's OHTTP relay? Is there a form, a DTS request, or a specific Apple program to apply to? I haven't found any documentation on this step. Any help appreciated.

Hello, Thank you for the hints — they were spot on. The trailing URL problem was indeed our issue: adding a trailing slash to our pirServerURL and pirPrivacyPassIssuerURL resolved the configurationInvalid error entirely. saveToPreferences() now works correctly for both enable and disable. We're now at a point where the URL filter is active (Enabled = YES confirmed in system prefs), but /queries are never reaching our PIR server. Looking at the configuration iOS applies: pirSkipRegistration = NO pirPrivacyProxyFailOpen = NO Our understanding is that with pirSkipRegistration = NO, iOS enforces Privacy Pass authentication via Apple's OHTTP relay before sending any PIR queries — and that relay will only forward requests to servers that have been registered/approved by Apple. Could you confirm this is correct? If so, what is the process to register our PIR server (https://dropbet-pir.fly.dev/) with Apple's OHTTP relay for use with NEURLFilterManager? Is there a form or a specific request channel for this? Thanks again.

Thank you for your previous guidance — I followed your advice and implemented NEURLFilterManager with the url-filter-provider entitlement (added via Signing & Capabilities → Network Extensions → URL Filter). My PIR server and Privacy Pass issuer are running at https://dropbet-pir.fly.dev, and the /.well-known/private-token-issuer-directory endpoint returns HTTP 200 with a valid response. However, when calling NEURLFilterManager.saveToPreferences() on a development build on my own device (iOS 26.5), I receive: NEURLFilterManager.Error code 1 — configurationInvalid Is this expected for a development build without the OHTTP relay, or does the entitlement require an additional approval step even for development testing? Best regards,

Thank you for your response. Two follow-up questions: The url-filter-provider capability does not appear in the Capability Requests tab of my developer portal. Could you advise how to request it for com.dropbet.DropBet (App Store ID: 6762567708)? Regarding the OHTTP relay onboarding form (developer.apple.com/contact/request/network-extension-url-filter): does the full PIR server + Privacy Pass infrastructure need to be deployed and running before submitting the form, or can the request be submitted earlier in the process? Best regards