I am seeking an actionable investigation path for an Apple Developer app enrollment failure that has remained unresolved since May 24, 2026.
The initial error was ID Verification Rejected. After support reset identity verification in May, I could proceed to the address screen, but pressing Continue produced "Action not allowed." I have reported the same failure on two Macs and an iPhone, including macOS 26 and macOS 27 beta, after reinstalling the app and with no VPN involved.
Support has received the requested screenshots and identity documentation, plus a recording and device details supplied on August 10. Multiple senior-advisor and operations escalations have not provided a resolution.
The unresolved question concerns trusted-device associations. In May, support reviewed my report that no unknown trusted devices were visible, reassured me and reset verification. In August, support asked me to contact owners of other Apple Accounts using my device as trusted, without identifying an actionable association or procedure. None of my devices has been used to enroll under another account.
I checked System Settings > Apple Account > Devices and Sign-In & Security > Two-Factor Authentication again on September 8. The verification list shows five Apple devices and one trusted phone number. That interface does not show associations with other people's accounts, so it cannot establish the state of Apple's internal enrollment checks.
Is there a supported process for Developer Relations or operations to investigate this cross-account association when the customer cannot identify another account? Which specific team or escalation path handles this? I am not requesting another person's private information or a way around enrollment requirements. I need Apple to identify the failing check and provide a remedy I can actually carry out.
More than three months without actionable findings is unacceptable. My existing support case contains the evidence and can be supplied privately to Apple staff.