I’m trying to submit my MCP app/connector for review, but I’m blocked by a generic validation error.
When I click “Submit for Review”, I get the message “This is a required field.” However, I have completed all visible fields across the App Info, MCP Server, Testing, Global, and Submit sections. I also completed identity verification recently and the verification status appears successful.
I’ve tried refreshing the page, signing out and back in, and checking for obvious missing fields, but the error persists. Browser console validation checks don’t reveal any invalid form fields either.
Has anyone encountered this issue before? Is there a way to identify which field the review submission process believes is missing, or could this be a backend validation bug?
Any guidance would be appreciated.
Same issue, i tried delete my draft and create a new draft still not working
tried multiple times by removing the draft and recreating it still no luck
I have the same problem. Last week I was able to add a screenshot and today I can’t.
Same wall here on a fresh app submission (Onplana, app ID asdk_app_6a27130db8348191a67935d531be4d2d). I tried both manual fill and uploading a complete chatgpt-app-submission.json with $schema: chatgpt-app-submission.v1.json, schema_version 1, all 236 tools with annotations + justifications, 5 positive test cases, 3 negative test cases. The form confirms “Imported 236 tool justifications. Skipped 0. Missing 0. Mismatched 0” and every visible field is populated, but Submit for Review fires the generic “This is a required field” toast with no field-level indication.
Network tab shows no submission API call goes out (validation is fully client-side; only /v1/rgstr telemetry pings fire). This matches what @CY-Anson found in the May 15 thread (1381013): backend reports “annotations for the added tool are missing” while the frontend collapses that to a generic required-field toast.
One observation that might be relevant for triage: our MCP server exposes 236 tools (large surface compared to most submissions). The form scans and creates 708 justification fields (236 × 3 hints). If the validator has any silent failure path on a single annotation entry, having more tools increases the surface area for the bug to bite. Would be useful to know if anyone hitting this has fewer than ~30 tools.
Looks like this is the same as this thread: ChatGPT App Submission form keeps showing “This is a required field” - #15 by AEj
It says it’s been resolved on their end, can you try again to verify?
i have raised a support ticket. its resolved now
Facing same issue on app submission.
Hey all, please check again, this should be resolved now!
