Troubleshoot SubmitCheck Apple access and failed checks

If the Apple connection fails

Confirm the selected key type and matching Key ID and .p8 file. For a team key, also confirm its Issuer ID. Check that the key is active and the associated account can access the intended app.

• Unauthorized: the credential or authentication could not be accepted.

• Forbidden or not authorized: access may be insufficient for the app or evidence category.

• Delayed or temporary failure: the source may be rate-limited or unavailable; follow the displayed retry guidance.

If the check cannot start

Confirm that you selected a valid sanitized SubmitCheck manifest within the displayed file limit, inspected the exact payload, and completed the confirmation. A raw build renamed as JSON is not valid evidence.

If evidence is incomplete

Review coverage and not-checked findings. Missing or failed source evidence must not become a pass. Reconnecting does not add unsupported evidence categories, and broader Apple roles are not a universal fix.

Escalate safely

Use SubmitCheck Support. Include the failing step, approximate time, report reference if available, and visible error. Do not attach raw builds, private keys, passwords, or tokens.