rn-harness-submit

rn-harness-submit — Phase 10: Store Submission

Submit the app to App Store and Google Play. Uses App Store Connect API (iOS) and Google Play Developer API v3 (Android).

Trigger

Called by the orchestrator as Phase 10.

Input

• docs/harness/config.md (API keys, developer info)
• docs/harness/handoff/build-result.md (build URLs)
• docs/harness/store-assets/ (screenshots + metadata)
• .env (credentials)

---

Part A: iOS — App Store Submission (Fully Automated)

A-1: Credential Check

Read from .env:

• ASC_KEY_ID — API Key ID (10 chars)
• ASC_ISSUER_ID — Issuer ID (UUID)
• ASC_PRIVATE_KEY_PATH — .p8 file path (default: ./credentials/asc-api-key.p8)

If missing or .p8 file not found → AskUserQuestion:

App Store Connect API Key is required.

1. App Store Connect → Users and Access → Integrations → API Keys
2. Generate new key (Admin role)
3. Save .p8 file to credentials/asc-api-key.p8
4. Add to .env:

   ASC_KEY_ID=XXXXXXXXXX
   ASC_ISSUER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
   ASC_PRIVATE_KEY_PATH=./credentials/asc-api-key.p8

Press Enter when done. (Type "eas" if already configured in EAS)

A-2: EAS Submit (Build Upload)

eas submit --platform ios --profile production --non-interactive

Or with specific build URL:

eas submit --platform ios --url [BUILD_URL] --non-interactive

A-3: App Store Connect API — Metadata

EAS Submit handles the binary upload. Additional metadata via ASC API:

1. Check/Create App Record

   • Check if Bundle ID exists → if not, register via POST /v1/bundleIds
   • Create app record via POST /v1/apps

2. Create App Store Version

   • POST /v1/appStoreVersions (version: "1.0.0", platform: IOS)

3. App Info

   • Primary locale: ko (Korean)
   • Primary category from PRD
   • Privacy policy URL: config.md → developer.privacy_url

4. Localization (ko locale)

   • App name (from title.txt), description (from full_description.txt), subtitle (from subtitle.txt)
   • Keywords (from keywords.txt) — MUST be 95-100 chars including commas.
     • Verify keywords.txt length before upload
     • If < 95 chars: return to screenshot phase to regenerate (don't waste ASO budget)
     • If > 100 chars: reject (API will fail)
   • Marketing URL: config.md → developer.homepage_url
   • Support URL: config.md → developer.email (or privacy URL)

5. Copyright

   • config.md → developer.copyright

6. Screenshot Upload

   • iPhone 6.7" screenshots only (supportsTablet: false → no iPad)
   • Create screenshot set → upload binary → commit

7. Build Assignment

   • Wait for build processing (processingState: VALID)
   • Link build to version

8. Review Information

   • Contact: config.md → ios_review (first_name, last_name, phone)
   • Demo account (if needed — AskUserQuestion)
   • Encryption: No (ITSAppUsesNonExemptEncryption: false)

9. Submit for Review

   • POST /v1/reviewSubmissions

A-4: iOS Result

iOS submission complete!
- App: [name]
- Version: 1.0.0
- Status: Waiting for Review
- App Store Connect: https://appstoreconnect.apple.com

---

Part B: Android — Google Play Submission

B-1: Manual Steps (API Limitations)

AskUserQuestion — PAUSE and guide user through mandatory manual steps:

Google Play requires some manual setup that the API cannot do.

Please complete these in Play Console (https://play.google.com/console):

1. CREATE APP:
   - App name: [name from PRD]
   - Default language: Korean
   - App (not game) / Free
   - Accept declarations

2. AAB UPLOAD (first time only):
   - Production → Create new release
   - Upload the .aab file from EAS Build
   - (Download link: [build URL from build-result.md])

3. CONTENT RATING (IARC):
   - App content → Content rating → Start questionnaire
   - Complete the survey

4. DATA SAFETY:
   - App content → Data safety
   - Fill out the privacy form
   - Note: If using AdMob, declare "Advertising" data collection

5. TARGET AUDIENCE & ADS:
   - Set target age group
   - Select "Yes, contains ads" (if AdMob enabled)

6. APP CATEGORY:
   - Store settings → App category
   - Select appropriate category

7. COUNTRIES/REGIONS:
   - Production → Countries/regions
   - Select distribution countries

Press Enter when all steps are complete.

B-2: Service Account Check

Read from .env:

• GOOGLE_PLAY_SA_JSON — path to service account JSON

If missing → AskUserQuestion:

Google Play Service Account JSON is required.

1. Play Console → Settings → API access
2. Create or link a service account
3. Grant "Release Manager" role
4. Download JSON key
5. Save to credentials/google-play-sa.json
6. Add to .env:

   GOOGLE_PLAY_SA_JSON=./credentials/google-play-sa.json

Enter the path, or press Enter if already set.

B-3: Generate publish.js Script

Create scripts/publish.js in the project based on the proven pattern:

#!/usr/bin/env node

const { google } = require('googleapis');
const fs = require('fs');
const path = require('path');

const PACKAGE_NAME = '[from config.md bundle_id]';
const KEY_FILE = path.resolve(__dirname, '..', process.env.GOOGLE_PLAY_SA_JSON || './credentials/google-play-sa.json');
const METADATA_DIR = path.resolve(__dirname, '..', 'docs/harness/store-assets/metadata');
const SCREENSHOTS_DIR = path.resolve(__dirname, '..', 'docs/harness/store-assets');

const APP_CONFIG = {
  contactEmail: '[from config.md developer.email]',
  contactWebsite: '[from config.md developer.homepage_url]',
  contactPhone: '',
  defaultLanguage: 'ko-KR',
};

// ... (full publish.js implementation)

Install dependency:

npm install googleapis

B-4: Prepare Metadata Files

Create metadata directory structure from store-assets:

docs/harness/store-assets/
├── metadata/
│   └── ko-KR/
│       ├── title.txt              # App name (from PRD)
│       ├── short_description.txt  # 80 chars max
│       ├── full_description.txt   # 4000 chars max
│       └── release_notes.txt      # What's new
├── icon.png                       # 512x512
├── feature_graphic.png            # 1024x500
└── android/
    └── phone/
        ├── phone_01.png
        ├── phone_02.png
        └── phone_03.png

B-5: Run Publish Script

Execute in stages:

# Step 1: Metadata + images only (no submission)
node scripts/publish.js --images

# Step 2: Verify in Play Console that everything looks correct

AskUserQuestion:

Metadata and images have been uploaded to Play Console.
Please verify in the Play Console that everything looks correct.

Press Enter to proceed with review submission, or type "skip" to submit manually.

# Step 3: Submit for review
node scripts/publish.js --submit-only --track production

B-6: Handle Draft Status

If the app is still in draft (first submission, manual steps incomplete):

• Script detects draft status automatically
• Updates release notes only (cannot submit draft via API)
• Prints warning with remaining manual steps:

⚠ App is still in draft status.
Complete these in Play Console before review submission:
  □ Content rating (IARC questionnaire)
  □ App category
  □ Countries/regions
  □ Data safety section

AskUserQuestion:

The app is in draft status — some Play Console steps are still incomplete.
Complete the items listed above, then press Enter to retry submission.
(Or type "done" to finish — you can submit manually from Play Console.)

B-7: Android Result

Android submission complete!
- App: [name]
- Track: production
- Version: [versionCode]
- Status: [completed/draft]
- Play Console: https://play.google.com/console

---

Part C: Final Wrap-up

C-1: Submission Report

docs/harness/handoff/submit-result.md:

# Store Submission Report

## iOS — App Store
- Status: [Submitted/Skipped/Failed]
- Version: 1.0.0
- Build: [buildNumber]
- Submitted: [date]

## Android — Google Play
- Status: [Submitted/Draft/Skipped/Failed]
- Track: [production/internal]
- Version Code: [versionCode]
- Submitted: [date]
- Script: scripts/publish.js

## AdMob
- iOS Ad Units: [real/test]
- Android Ad Units: [real/test]
- Note: [Replace test IDs before release if using test IDs]

## EAS Update
- Channel: production
- OTA ready: [yes/no]

## Pending Manual Actions
- [ ] [remaining items]

## Re-submission Commands
# Update metadata + images
node scripts/publish.js --images

# Submit for review
node scripts/publish.js --submit-only

# Full automation
node scripts/publish.js --images --submit

# Internal test track
node scripts/publish.js --images --submit --track internal

C-2: Git Tag

git tag -a v1.0.0 -m "Release 1.0.0 — Store submission"

AskUserQuestion before pushing tag:

Ready to create git tag v1.0.0. Push to remote? (yes/no)

State Update

status: completed
current_phase: done

HARD GATES

• iOS: EAS build must succeed before submission
• Android: Manual Play Console steps must be confirmed before API calls
• Screenshots and metadata must exist before submission
• Privacy policy URL required for both stores
• Service Account JSON must exist and be valid for Android API calls
• Draft app detection: gracefully degrade to release notes update only
• Submission failure: analyze error, report to user, do NOT retry blindly
• publish.js must be generated with correct package name and config values