We have had our app UPDATE rejected now 4 times, because the review took so long, that in the meanwhile either the required MCP contract or the entire plugin submission flow has changed.
The rejection only states that one or more test cases failed. It does not identify the failing test, the observed behavior, or the expected result. We have rerun the submitted cases across multiple operating systems on both mobile and desktop, and they work consistently for us.
Could the review team please clarify:
- Which exact test case failed?
- What behavior was observed, and what was expected instead?
- Which MCP contract and submission requirements were used during the review?
- Why are updates to an existing approved app not eligible for an accelerated review when the publisher and core functionality remain unchanged?
We are happy to correct any reproducible issue, but without actionable feedback, it is difficult to determine what needs to change.