---
id: mobile-firebase-distribution
title: Firebase App Distribution / Pre-launch / App Review
category: Coding
status: draft
source_trust_level: B
verification_status: conceptual
created_at: 2026-05-09
updated_at: 2026-05-09
tags: [mobile, firebase, vibe-coding]
tech_stack: { language: "process", applicable_to: ["Mobile"] }
applied_in: []
aliases: [Firebase App Distribution, Pre-launch report, App Store review, common rejections, expedited review]
---

# Firebase Distribution / Pre-launch / Review

> Beta tester + automated test + store review. **Firebase App Distribution (cross-platform), Pre-launch report (Android), App Store review tips**.

## 📖 핵심 개념
- Firebase Distribution: free, cross-platform.
- Pre-launch report: 자동 device test (Android).
- Apple App Review: 1-2 days, common rejection.
- Expedited review: emergency fix.

## 💻 코드 패턴

### Firebase App Distribution setup
```bash
firebase login
firebase init appdistribution
```

### Distribute (CLI)
```bash
# Android
firebase appdistribution:distribute app/build/outputs/apk/release/app-release.apk \
    --app 1:1234567890:android:abcdef \
    --release-notes "Bug fixes" \
    --groups "internal-testers"

# iOS
firebase appdistribution:distribute MyApp.ipa \
    --app 1:1234567890:ios:abcdef \
    --release-notes "Bug fixes" \
    --testers "alice@example.com,bob@example.com"
```

### Fastlane integration
```ruby
lane :distribute do
  build_app
  firebase_app_distribution(
    app: 'YOUR_APP_ID',
    groups: 'internal',
    release_notes: 'Bug fixes',
  )
end
```

### Tester groups
```bash
firebase appdistribution:groups:create internal
firebase appdistribution:testers:add --group internal alice@example.com
```

→ Email 가 group 식. Group → distribute.

### Tester experience
```
1. Email "Beta available".
2. App Tester app (iOS / Android) 다운로드.
3. App Tester 가 list.
4. 1-tap install.
5. Feedback button (in-app screenshot).
```

### vs TestFlight / Play Internal
```
Firebase:
- Cross-platform (1 tool 둘 다).
- Free.
- 작은 ecosystem.

TestFlight: iOS 전용, Apple 친화.
Play Internal: Android 전용, Google 친화.

→ Cross-platform team 가 Firebase.
```

### Firebase Crashlytics 통합
```swift
// iOS
import FirebaseCrashlytics
Crashlytics.crashlytics().log("Login attempted")

// Force crash for test
fatalError()
```

→ Beta crash 가 자동 보임.

### Pre-launch report (Android)
```
Play Console → App → Pre-launch reports.

업로드 후 (15-30 min):
- Crash report (다른 device, 다른 Android version)
- Performance metric
- Accessibility issue
- Security warning

→ 매 실 device 가 5 min 자동 navigate.
```

### Pre-launch login (auto fill)
```
Play Console → Setup → Pre-launch report credentials.
- Test username + password.
- Robo crawler 가 사용.
```

→ Login 후 page 도 test.

### Robo script (custom)
```json
{
  "actions": [
    { "type": "click", "elementText": "Login" },
    { "type": "input", "elementId": "email", "text": "test@example.com" },
    { "type": "input", "elementId": "password", "text": "password" },
    { "type": "click", "elementText": "Submit" }
  ]
}
```

→ Custom flow test.

### App Review 준비
```
- App icon (1024x1024)
- Screenshot (모든 size)
- App preview video (선택)
- Description (4000 char)
- Keyword (100 char)
- Support URL
- Privacy URL
- App Store Connect 의 Test Information

→ 매 항목 가 review checklist.
```

### Common Apple rejections
```
1. Crash (가장 흔한). Fix → resubmit.
2. Metadata mismatch (screenshot ≠ app).
3. Functionality (broken feature).
4. Privacy (NSUsageDescription 누락).
5. Sign in with Apple (3rd party login + 가).
6. Subscription (clear pricing).
7. Hidden purchase (IAP outside StoreKit).
8. Misleading (hyperbolic claim).
9. Info.plist key 누락.
10. Beta software (not production-ready).
```

### Privacy nutrition label
```
App Store Connect → App Privacy.
- Data linked to user (track)
- Data not linked (analytics)
- Data used for tracking (advertising)

→ 정확 작성.
```

### App Tracking Transparency
```swift
// Track 하기 전:
import AppTrackingTransparency

ATTrackingManager.requestTrackingAuthorization { status in
    if status == .authorized {
        // Track
    }
}
```

```xml
<key>NSUserTrackingUsageDescription</key>
<string>Used for personalized ads.</string>
```

→ iOS 14.5+ 의무. Reject 흔함.

### Sign in with Apple
```
ToS: 다른 social login (Google, Facebook) + 가 있으면 Apple 도.
- Skip 가능 = 거의 모든 login flow 가 추가.
- Native UI 가 Sign in with Apple button.
```

### Expedited review
```
App Store Connect → Resolution Center → Request expedited review.
이유:
- Critical bug (사용자 영향)
- Time-sensitive (event)
- Legal / regulatory

→ 보통 24 hr 안 review.
1년 1-2회 만.
```

### App Review reply
```
Reject → Resolution Center.
- 명확 답.
- "Fixed in build 1.5.0" 식.
- Screenshot / video 가 도움.

→ 며칠 후 재 review.
```

### Beta 의 app store 가 다름
```
TestFlight beta 가 review (1-2 day, first build only).
이후 build = quick review (몇 hour).

App Store full review 가 1-2 day.
```

### Phased release (App Store)
```
Submit → Approve → Phased release:
- Day 1: 1%
- Day 2: 2%
- Day 3: 5%
- Day 4: 10%
- Day 5: 20%
- Day 6: 50%
- Day 7: 100%

→ 매 day crash 가 지키면 halt 가능.
```

→ Bug 발견 = halt + new build (expedited).

### Play Store review
```
Apple 보다 빠름 (1-3 hour 평균).
Manual review:
- Permissions (특히 background location).
- Privacy policy.
- Restricted content.

매 update = same.
```

### Version bump
```
1.2.3 → 1.2.4 (patch)
1.2.4 → 1.3.0 (minor)
1.3.0 → 2.0.0 (major)

Build number 가 매 upload (CFBundleVersion).
```

→ TestFlight 가 build number 만 다르면 OK.

### Reject → fix flow
```
1. Reject 받음 (email + Resolution Center).
2. 이유 분석 (screenshot, log).
3. Fix code.
4. New build (build number++).
5. Same version 또는 patch 상승.
6. Resubmit.
7. Quick re-review (1 day).
```

### Apple Developer Forum
```
forums.developer.apple.com
Common rejection 검색.
"Guideline 4.0 — Design" 식 search.
```

### App Store Connect API
```bash
# CLI 로 metadata update / build upload
xcrun altool --upload-app -f app.ipa --apiKey ABC --apiIssuer XYZ
```

→ Fastlane 가 wrap.

### 함정: Privacy 변경
```
Update 가 새 SDK 추가:
- 새 tracking?
- 새 data collection?
- App Privacy 항목 update.

→ App Privacy 와 actual code 가 mismatch = reject 위험.
```

### 함정: Subscription
```
- Free trial 명확.
- Auto-renew 명시.
- Cancel link.
- Restore purchase button.

→ Subscription rejection 흔함.
```

### Test build 가 reject?
```
TestFlight first build = review.
- Production-quality.
- Crash 없음.
- Required content.

→ "test only" 라도 quality.
```

## 🤔 의사결정 기준
| 작업 | 추천 |
|---|---|
| Cross-platform beta | Firebase App Distribution |
| iOS only | TestFlight |
| Android only | Play Internal Track |
| Auto Android test | Pre-launch report |
| Critical fix | Expedited review |
| Slow launch | Phased release |
| Manual review concerns | Common rejection 검색 |

## ❌ 안티패턴
- **Production 가 first beta**: bug 가 모든 사용자.
- **NSUsageDescription 누락**: reject.
- **Hidden purchase**: reject + ban.
- **Misleading screenshot**: reject.
- **Privacy nutrition 가짜**: 사용자 신뢰 ↓.
- **No phased release**: bug 가 100%.
- **Reject 자주 무시**: 시간 낭비.

## 🤖 LLM 활용 힌트
- Firebase Distribution = cross-platform free beta.
- Pre-launch report = Android free auto-test.
- App Review checklist 매번.
- Phased release + crash monitor = safe.

## 🔗 관련 문서
- [[Mobile_TestFlight_Distribution]]
- [[Mobile_App_Store_Optimization]]
- [[Mobile_Crash_Free_SLO]]
