REWRITEBETA

After your handoff

Launch guide.

From your handoff zip to TestFlight and the App Store — in plain language. Rewrite gave you native iOS source and artifacts for the scope you approved. Shipping on the App Store happens on your Mac and your Apple developer account — certificates, listings, and review are yours to run. This guide is engineering orientation, not legal or compliance advice; get professional help for regulated products (health, payments, kids, etc.).
1

Get a build you trust in Xcode

  1. ●Open your project in Xcode on a Mac and resolve any remaining wiring (API base URL, OAuth, polish).
  2. ●Run on Simulator, then on a physical device — device builds catch signing and entitlement issues early.
  3. ●Confirm Bundle ID is what you want long-term — changing it later is painful.
  4. ●Set Version (user-facing) and Build (must increase for every upload to Apple).
2

Signing (Apple Developer Program)

  1. ●Enroll in the Apple Developer Program if you haven't ($99/year at time of writing).
  2. ●In Xcode: Project → Signing & Capabilities → pick your Team, set Bundle Identifier to match App Store Connect.
  3. ●Prefer Automatically manage signing unless your org uses manual profiles.
  4. ●Enable only capabilities you need (Push, Associated Domains, etc.) — each can require extra portal setup.
3

Create an archive and upload

  1. ●Select Any iOS Device (arm64) or a connected iPhone — not Simulator-only — as the run destination.
  2. ●Product → Archive. When the Organizer opens, Distribute App → App Store Connect (for TestFlight / App Store).
  3. ●If upload fails, common fixes: bump build number, refresh signing in Xcode Accounts, fix version conflicts in App Store Connect.
4

App Store Connect — app record and compliance

  1. ●In App Store Connect, create the app if needed; Bundle ID must match Xcode exactly.
  2. ●Complete App Privacy (data collection) truthfully — it feeds the App Store nutrition labels.
  3. ●Plan screenshots and description for the device sizes you support; Apple requires assets per size class you claim.
5

TestFlight (beta)

  1. ●After upload processing completes, the build appears under TestFlight.
  2. ●Answer export compliance / encryption questions when prompted (many apps use standard exemptions; read Apple's questionnaire carefully).
  3. ●Internal testers (your team) can install quickly. External testers may need Beta App Review for the first build of a version.
  4. ●Install Apple's TestFlight app on devices, accept invites, install builds.
6

Submit to the App Store

  1. ●When you're ready for production, create a version in App Store Connect, attach the build, and complete required metadata.
  2. ●Submit for review. Apple's App Review Guidelines apply — allow time for feedback and resubmits.

When something fails

SymptomWhat to check
Signing errorsTeam, Bundle ID, cert expiry — Xcode Settings → Accounts to refresh.
Upload rejectedBuild number already used; bump build and archive again.
Processing stuckWait; if it fails, read the email from Apple for the specific binary issue.
Compliance promptsFinish encryption / export questions in App Store Connect.

Deeper reference

Rewrite supplies code and handoff artifacts; your team owns Apple accounts, signing, store listing, and compliance.