Use the SubmitCheck checklist, requirements, and submission pack
Review manual decisions and export the evidence belonging to a completed report.
Written By Enrique Bonansea
Last updated About 2 months ago
Open a completed report first
The Checklist, Requirements, and Submission pack views depend on a selected report. An empty state in these views can mean no report has been selected or completed; it does not mean the submission has no issues.
Checklist
Use Checklist for evidence that requires a human decision. Review each item in the context of the selected app, build, and intended behavior. A manual confirmation does not supply missing automated evidence.
Requirements
Requirements shows the official source references and rule versions associated with the report. Reports remain tied to the source snapshots and rules used when they were generated. Review the current official source if you are preparing a later submission.
Submission pack
Open Submission pack to review the export options available for the selected completed report. Exports are derived from that report’s sanitized evidence. Check the app identity, version, date, and unresolved findings before sharing an output.
A submission pack is supporting documentation. It does not upload a build, edit App Store Connect, submit your app, or certify Apple approval. Review exported material for private information before sharing it.
Was this helpful?
More in SubmitCheck
Getting started with SubmitCheckCreate a sanitized SubmitCheck manifest locallyConnect App Store Connect to SubmitCheckImport a manifest and run a SubmitCheck submission checkStill need help? Ask the team