Get early access
How it works

From Your Repo to Waiting for Review — What AscAuto Actually Automates

Connect a GitHub repo and an official App Store Connect API key, and AscAuto can carry a build through five phases: cloud build, TestFlight, a full submission-readiness check, a one-click Submit for Review, and — if Apple pushes back — automatic diagnosis, fix, and resubmission. You approve every listing change and every submission; nothing reaches Apple silently.

Last updated: July 2026

The five phases

01
Connect
Install the AscAuto GitHub App on your repo and add your official App Store Connect API key (issuer ID, key ID, .p8 private key). The key is AES-256-GCM encrypted at rest and only decrypted in memory when it's actually used — never your Apple ID password.
02
Cloud build
AscAuto opens a pull request on your repo adding a GitHub Actions build workflow and generates your distribution signing certificate. Push a version tag and the workflow builds, signs, and uploads the processed build straight to TestFlight — no local Xcode Archive step.
03
Submission Copilot
AscAuto scans your App Store Connect listing for everything Apple checks before it will accept a review: App Review contact info, export compliance, screenshots and description, the age-rating questionnaire, App Privacy labels, primary category, and price. Anything missing gets an AI-drafted fill built from your actual app — you review every field before it's written, and nothing is applied without your click.
04
Submit for Review
Once every check is green, hit Submit for Review. AscAuto re-scans live at that exact moment — no stale data — attaches your latest processed build, and only then moves your version to Waiting for Review through Apple's official reviewSubmissions API. If something's not actually ready, it tells you what's blocking instead of submitting.
05
If Apple rejects it
AscAuto reads whatever Apple sends back, classifies the guideline, and drafts the fix. Safe metadata fixes resubmit automatically above the confidence threshold you set. Code-level issues become a GitHub pull request — you merge, AscAuto resubmits. Reviewer information requests get a drafted reply that only sends after your approval. The loop repeats until it's approved.

What's still yours

Nothing happens without you
  • Every listing change and the final Submit for Review need your click — no silent auto-submit flag exists.
  • Code fixes ship as pull requests. Nothing merges without you.
  • You own the GitHub repo, the signing certificate, and the App Store Connect account throughout. Revoke the API key from Apple's side at any time and everything stops.

FAQ

Does AscAuto submit my app the first time, or only handle rejections?

Both. Connect a GitHub repo and an App Store Connect API key, and AscAuto can go from a tag push to Waiting for Review with no manual App Store Connect work. If you'd rather keep uploading and submitting yourself, that still works — AscAuto just handles whatever Apple sends back. See what changes if you submit yourself.

Is this actually one click, or does AscAuto act on its own?

Every listing change and the final Submit for Review require your click by design. Only metadata fixes above the confidence threshold you set can auto-apply after a rejection — nothing reaches Apple's review queue silently.

What if I only want the cloud build, not the auto-submit?

That's fine. You can stop after TestFlight — Submission Copilot only scans, drafts, and submits when you use it.

Do I need to give AscAuto my Apple ID password?

No, never. AscAuto authenticates with an official App Store Connect API key (.p8), AES-256-GCM encrypted and revocable from Apple's side at any time.

What happens after Apple approves the app?

Nothing — AscAuto only acts when there's a submission check to run or a rejection to resolve. A clean approval means there's simply nothing left to do.

Connect your repo. Let AscAuto take it to Waiting for Review.
Cloud build, submission checks, and rejection handling — one connection, your approval at every step that matters.
Get early access

Related guides

Comparison
AscAuto vs Fastlane — which one fits you
Submit it yourself
What changes if you keep using Xcode or Transporter
All guides
Every common App Store rejection guideline
FAQ
Security, permissions, and pricing