NEURL Filter configuration approved under wrong Developer Team — resubmission blocked by duplicate domain

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.

So a fresh submission is technically impossible

Ah, tricky. I’m investigating whether there’s a way out of this bind.

if I open a paid Technical Support Incident (TSI) for this

DTS hasn’t accepted paid TSIs since May 2024. Rather, we now have code-level support requests, which are all free (although we redirect most of them to the forums, so thaht everyone can benefit from our work).

But…

Or would it likely get bounced as "out of scope" … ?

Indeed. However, in a case like this, where the correct path forward isn’t clear, DTS might’ve accepted your TSI. And the equivalent is me wading into this forums thread.

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

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!

OK, I have a plan (-:

Please file a bug requesting that we transfer the configuration from the current team to your organisation team. Make sure to include:

• The old Team ID
• The new Team ID
• The original request UUID

Once you’re done, please open a DTS code-level support request, making sure to reference this thread. I’ll use that to do some checks and then make sure you bug gets routed to the right folks.

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

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

Thanks. I’ll be in touch via your DTS case.

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

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.

Yeah, sorry about the delay on my side. I’ve been in and out of the office this past month.

Looking at FB24607828 I don’t see anything to be concerned about. PIR onboarding takes time, even for normal requests.

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

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?

it's purely a matter of reassigning the existing approved config to the correct team.

… and waiting for that to be onboarded.

Previously the wrong team was approved but not onboarded. FB24607828 is a request to transfer the approval to the right team, but it still has to wait for onboarding. That can take a while.

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

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.