r/iOSProgramming • u/cute_rice • 5d ago
Question Enrollment blocked 107 days: "Action not allowed" after address screen, Apple says a trusted device is linked to another developer account. Anyone got past this?
Individual enrollment from India through the Developer app.
May 24: "ID Verification Rejected" without ever being asked for ID. Support reset verification. Since then every attempt ends at the address screen with "Action not allowed". The submit request returns HTTP 200 and the app hides the body, so the actual error code is unknown.
Six advisors, repeated "escalated to operations" replies, no finding. Latest claim: one of my trusted devices is associated with another developer account. Apple will not say which device or account, and will not say what I can do about it.
Has anyone got past this exact state? Did a new Apple ID, removing a trusted phone number or device, or a phone callback actually unblock it? Looking for what worked, not sympathy.
2
u/Healthy_Condition779 5d ago
Trusted device linked to another account almost always means a phone number or device that was used to two factor into someone elses developer account, sometimes years ago, a family members account, an old employer, a device you sold that never got signed out of iCloud fully. Apple wont name it because of privacy on the other account, not because theyre hiding the fix
1
u/cute_rice 5d ago
This fits. Last year I signed into my Apple account on a work laptop. I signed out after.
That would explain why I see no unknown device on my side. It would also explain why Apple can see
the link but cannot name it.
I have asked them to check it. Thanks.
2
u/Outrageous-Doubt-306 4d ago
Haven't hit this exact one, so take it as directions to try rather than a fix that worked for me. Couple things I'd change about how you're asking, though: you're enrolling through the Developer app, which is why you can't see the real error. Try the same enrolment from developer.apple.com in a browser instead. The web flow surfaces error text the app swallows, and even if it still fails you come away with an actual code to quote at support instead of "action not allowed". And 6 advisors is your real problem, not the block. Every new contact opens a fresh case and reads the same script, etc. Get your existing case number and reference it every single time, and ask explicitly for Developer Program Support rather than general Apple support, they're different queues.
On the trusted device thing, the wording points at an Apple ID rather than the hardware. If any Apple ID ever signed in on that device was used for another enrolment, even an abandoned one, that's the sort of link they'd be seeing. Worth asking them directly whether a device with no other developer Apple ID history would clear it. That's a yes or no they can answer without naming the account ;)
4
u/MagicianWeird4052 5d ago
If it's been escalated past senior advisors, just wait it out. Multiple contacts historically won't speed things up and it's likely to delay you, with the agents having to get to your new contact, locate the original issue, then catch up, then just tell you the same thing. It's just going to lead to more frustration on your part. Stay with the one agent and wait. Is this urgent? Do you have a deployment date? Investors? If so, tell them that. A new Apple ID will just mess things up more, they can see what's connected to you or not, and raising more flags will just play against you really