IDENTITY-001VERIFIED PASSname, slug, version, ios.bundleIdentifier and ios.buildNumber all present and non-empty.
Evidence: app.jsonTHE FIELD GUIDE + AGENT AUDIT PACK
A 42-page field guide and a 31-check agent audit pack. Work through real Apple messages, App Store Connect screens and practical release tests—then ask your coding agent to inspect the repository evidence.
$29 USD one-time for the complete bundle No subscription
Edition 1.1 · Guide + agent pack v0.3.2.
The Expo App Store
Submission Playbook

A clear next stepFrom store setup to reviewer access.
Lessons from real submissionsThirteen field cases to help diagnose problems.
Read it your wayRead the guide. Run an evidence-based agent audit.
Look inside
Take a look at the actual pages. Each one turns a submission task or a confusing symptom into something you can check.
Creating your first subscription and including it for review are different steps. This page shows where to check, what can be missing, and what completed work looks like.
From the guideThe app’s paywall works in development. Products exist in App Store Connect. The first submission still does not include those products for Apple to review.
A real Terms of Use message, followed by the fields to inspect and a response template. The case separates Apple’s observation from the proposed fix.
From the guideFor a standard EULA, follow Apple’s direction to include the terms link in the description. For a custom license, inspect the relevant App Store Connect field. Check the correct locale and saved version.
Your coding agent gets a playbook too
Run a read-only audit with 31 App Store checks. Then use the guide to close the questions that require the store dashboard or a real device.
IDENTITY-001VERIFIED PASSname, slug, version, ios.bundleIdentifier and ios.buildNumber all present and non-empty.
Evidence: app.jsonCOMPAT-002VERIFIED FAILpatchedDependencies pins react-native@0.79.2, but 0.81.5 is installed; one dependency is a different SDK major from the rest.
Evidence: package.jsonARTIFACT-001UNRESOLVEDNo .ipa or .app supplied, so DTPlatformName cannot be verified. Provide the exact submission artifact.
Evidence: Submission artifact not suppliedEarlier Claude Code sample (v0.1.1). Included pack: v0.3.2, 31 checks. Full provenance is in the linked report.
Read the report and methodologyOne small, practical bundle
Follow the walkthrough the first time. Return to the checklist for the next release.
42-page PDF · Printable checklist · Copyable templates · Agent pack
Nine walkthroughs and nine practical labs, with real App Store Connect screens. Trace purchases, test the release and assemble a clear submission record.
Work through launch failures, purchase problems, missing metadata and reviewer access. Read actual Apple correspondence alongside the investigation. Cases without a primary message are labeled as internal notes; one covers an account incident caught before rejection.
Keep a one-page final checklist, a release record, purchase map, reviewer notes and a factual response template for rejection recovery.
Give your coding agent a structured audit: 31 App Store checks, 30 supporting rules, 13 field patterns and an 11-step runbook. Every finding needs evidence and a next action.
Keep your downloaded edition. Request updated files by email with your receipt number during the first year. Best-effort support covers file defects; app audits and submission services are not included.
Made for your last mile
For a solo developer preparing an Expo or React Native iOS submission, especially a first app with subscriptions.
The guide works without an AI account. You bring the app and your Apple developer account; it gives you a sequence to work through.
The agent pack includes 31 App Store checks, 30 supporting rules and an 11-step runbook. It contains no executable. You still verify the store configuration and test the final app.
Frameworks: Guide: Expo / React Native iOS submission. Agent compatibility table: Expo SDK 52 through 57. Newer SDKs remain unresolved; the table does not establish current Apple build compliance.
Agents: Works as ordinary Markdown. Three adapters ship: Claude Code, a generic AGENTS.md block (which is what Codex and other AGENTS.md-aware tools use), and a Cursor rule. No universal automatic install is claimed, and no agent-specific adapter beyond those three.
It never signs in to or reads your App Store Connect account. You verify the store setup and test the final app.
See the agent report and its provenanceThe complete playbook
PDF guide, checklist, templates and the agent pack. All in one download.
12 months of updates included.
14-day refund window, even after downloading.
$29 one-time for the PDF playbook and agent pack. Download after payment.
Read the terms and refunds.
A 42-page PDF playbook, a printable checklist, copyable templates and an agent audit pack with 31 evidence-backed checks. The PDF works without an AI subscription.
Yes. The guide covers Expo and React Native iOS submissions. The agent pack’s compatibility table covers Expo SDK 52 through 57; newer SDKs need a separate check against current requirements.
No. The skill is a read-only audit protocol with no executable code, no network requirement, no credentials, and no App Store Connect access. External facts remain unresolved until you provide evidence.
No. It catches avoidable submission blockers and separates verified facts from developer confirmations and unresolved checks. Apple alone decides whether an app is approved.
The PDF and templates work on their own. The agent pack uses your existing coding agent; adapters are included for Claude Code, Cursor and AGENTS.md workflows. The sample shows an earlier Claude Code run; current cross-agent validation is still pending.
No. $29 USD is a one-time purchase, with 12 months of updates. Your downloaded edition remains yours.
The PDF playbook, printable checklist, templates and agent pack download together after payment, from the confirmation page.
Request a full refund within 14 days of purchase by emailing your receipt number to hello@vertostudios.com.