Why a SubmitCheck rule is marked not checked

Not checked means SubmitCheck could not safely evaluate a rule with the evidence and capabilities available. It is not a pass and is not proof that the app violates the requirement.

Common causes

• No App Store Connect evidence was collected.

• The key or associated user cannot read the required app or evidence category.

• The relevant Apple endpoint or evidence type is not currently supported.

• A request failed, was delayed, or returned evidence that could not be used.

• The selected artifact and Apple records do not provide the information required by that rule.

Artifact-only reports

You can run an artifact-only report. Its App Store Connect and cross-source rules remain not checked because the required submission evidence is absent. An artifact-only success must not be interpreted as ready to submit.

What to do next

Inspect the finding’s evidence and coverage explanation. Correct the connection or selection when appropriate, or perform the required manual review. Do not request broader Apple permissions merely to make the status disappear; use the minimum supported access and contact support when coverage is unclear.