I am currently blocked from submitting an application through our Apple Developer Organization account because of an error with the MRDP (Model Reporting Rules for Digital Platforms) compliance form in App Store Connect.
When I go to:
App Store Connect → Business → Add Information
Apple opens the MRDP compliance form. The form asks whether our apps provide personal services. For our application, the appropriate answer is No.
However, when I select No and try to complete the form, App Store Connect displays:
"We are currently unable to process your request. Please try again later."
This is not a browser/cache issue.
I have reproduced the exact same problem using:
- Chrome
- Chrome Incognito
- Safari
I also checked the browser Developer Tools, and the request to Apple's MRDP endpoint is returning HTTP 403. Specifically, the request to the /ppm/complianceform/.../formConstraints endpoint is being rejected by Apple's server.
The result is that I cannot complete the MRDP requirement and therefore cannot proceed with submitting the application.
I have already contacted Apple Developer Support about this issue, but I am concerned that the issue is not actually being reviewed because the responses/support process has been extremely slow and, in some cases, completely unresponsive.
What I need from Apple
This appears to be an App Store Connect backend/account-state problem, rather than something that can be resolved by changing browsers or clearing cookies.
Could someone from the App Store Connect/MRDP engineering or account team please investigate why the formConstraints request is returning HTTP 403 for our organization account?
We simply need to complete:
MRDP → No → Done
but Apple's backend prevents us from doing so.
This is currently blocking an actual App Store submission, so I would really appreciate either:
- A fix to the MRDP compliance form/account state, or
- Escalation to the team responsible for the
/ppm/complianceformservice.
If anyone from Apple is able to look into this, I can provide the relevant support case number and screenshots privately rather than posting account-specific information publicly.
This has already been reproduced across multiple browsers, so please do not simply suggest trying another browser or clearing cache. The HTTP 403 response from Apple's own endpoint indicates that the request is being rejected server-side.