App Store Guideline 2.3.11 explained: Pre-order accuracy

Guideline 2.3.11 sits in Apple's Performance section and is most relevant to submission completeness and reviewer access.

This page summarizes the review risk in practical terms and links to the official Apple source for the exact rule text.

Apple needs to review a final, functional build with complete metadata and working services.

Apple needs to review a final, functional build with complete metadata and working services.

Reviewers should have enough access to evaluate account-based, paid, or non-obvious features.

Temporary content, broken URLs, unavailable backends, and missing demo data can delay review.

The app crashes, shows placeholders, or depends on a backend that is not available during review.

Apple cannot log in, reach a feature, test an IAP, or understand a non-obvious flow.

Metadata or URLs are incomplete, broken, or not production-ready.

Test the build on device and remove placeholder or test-only content.

Provide demo credentials, demo mode, sample data, or hardware instructions.

Write review notes that give Apple a tap-by-tap path to important features.

If Apple cited Guideline 2.3.11, reply with the exact change you made and where the reviewer can verify it.

If you believe the app already complies, provide concise evidence, navigation steps, and any supporting documentation instead of a generic appeal.

Keep the tone factual and cooperative. Avoid promising approval or arguing beyond what the submitted build and metadata can prove.