After your handoff

Launch guide.

From your handoff zip to TestFlight or Google Play internal testing and the App Store or Google Play — in plain language. Rewrite gave you native iOS and Android source and artifacts for the scope you approved. Shipping on the App Store or Google Play happens on your Mac (iOS) or in Android Studio (Android) with your developer accounts — 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.).

iOS — Xcode, TestFlight, App Store

1

Get a build you trust in Xcode

  1. ●Open your project in Xcode (iOS) on a Mac and resolve any remaining wiring (API base URL, OAuth, polish).
  2. ●Run on the iOS Simulator (Mac), 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 / the 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.

Android — Android Studio, internal testing, Google Play

7

Get a build you trust in Android Studio

  1. ●Open your project in Android Studio (the folder with settings.gradle.kts) and let Gradle sync finish.
  2. ●Run on an Android emulator, then on a physical phone (USB debugging on) — real devices catch problems emulators hide.
  3. ●Confirm the application id in app/build.gradle.kts is what you want long-term — changing it later means a new Play listing.
  4. ●Set versionName (user-facing) and versionCode (must increase for every upload to Google Play).
8

Signing (your release key)

  1. ●Create a keystore once: Build → Generate Signed App Bundle / APK → Create new…. Back up the file and passwords somewhere safe.
  2. ●Copy keystore.properties.example to keystore.properties and fill in the path and passwords — Gradle picks it up automatically.
  3. ●When you create the app in Google Play Console, accept Play App Signing — Google holds the final key; yours becomes a resettable upload key.
9

Build the bundle and upload

  1. ●Build a release App Bundle (Build → Generate Signed App Bundle or ./gradlew bundleRelease). Google Play accepts .aab files, not raw APKs.
  2. ●In Google Play Console, create the app if needed (one-time $25 developer registration).
  3. ●Go to Testing → Internal testing → Create new releaseand upload the bundle — Google Play's equivalent of TestFlight.
10

Play Console — listing and compliance

  1. ●Complete the Data safety form and content rating questionnaire — drafts live in PlayStore/ in your handoff zip.
  2. ●Plan screenshots and store listing copy for the phone sizes you support.
  3. ●Add yourself as an internal tester, accept the opt-in link on your phone, and install from Play.
11

Internal testing (beta)

  1. ●After upload processing completes, the build appears under Internal testing.
  2. ●Install from the tester link on real devices — no separate beta app like TestFlight; it comes from Google Play.
  3. ●Closed testing (wider group) may be required before a public release for newer personal developer accounts — plan 12+ testers for 14 days if that applies to you.
12

Submit to Google Play

  1. ●When you're ready for production, promote a tested release to Production and complete any remaining Play Console checks.
  2. ●Google's Developer Program Policies apply — allow time for review and resubmits.

When something fails

iOS

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.

Android

SymptomWhat to check
Gradle sync failsFile → Sync Project with Gradle Files; update Android Studio if it's old.
Wrong signing keyUse the same keystore as the first upload, or request an upload-key reset (Play App Signing).
Version code already usedBump versionCode in app/build.gradle.kts, rebuild, re-upload.
Release button greyed outFinish Data safety, content rating, and listing assets in Play Console.

Deeper reference

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