PricingLoginStart free
React Native Academy · 강의

심사 제출 및 거부에 대응하기

EAS Submit 또는 Transporter로 빌드를 업로드하고 App Store Connect에서 심사용으로 선택하며, 가장 흔한 거부 사유와 해결 방법을 이해합니다.

레슨 4/413개 단계

심사 제출 및 거부에 대응하기은(는) CoddyKit의 무료 React Native Academy 강의입니다. 이것은 4개 중 4번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 React Native Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

The App Review Process

After you submit your app for review, Apple's App Review team manually and automatically tests it against the App Store Review Guidelines. Review times average 1–3 business days for a first submission and often less for updates. You can check the status in App Store Connect: Waiting for Review, In Review, Ready for Sale, or Rejected. Apple may ask clarifying questions via the Resolution Center before completing the review.

Submitting the Build for Review

With all metadata complete and a build selected, click Add for Review in App Store Connect, then Submit to App Review. Apple checks you answered all legal questions (export compliance, content rights, content rating). Once submitted you receive an email confirmation. The app moves to Waiting for Review — you cannot edit metadata while it is under review, but you can remove the submission and resubmit if you catch a critical issue.

# Alternatively, use EAS Submit to upload AND trigger review:
eas submit --platform ios --latest

# EAS submit options:
# --latest           Use the most recent build
# --id <build-id>    Submit a specific build
# --non-interactive  For CI pipelines

# Check submission status:
eas submission:list --platform ios

Common Rejection Reasons

Understanding common rejection reasons helps you avoid them proactively. The most frequent causes are: crashes during review (test thoroughly before submitting), broken links in the support/privacy URL, misleading screenshots that don't match actual app behavior, missing functionality (the reviewer cannot log in without test credentials), and privacy guideline violations (collecting data without disclosure or user consent).

// Top rejection categories (from Apple data):

// Guideline 2.1 - App Completeness:
//   Crashes, broken links, test content visible in production

// Guideline 4.0 - Design:
//   UI that doesn't match screenshots, placeholder text left in

// Guideline 5.1 - Privacy:
//   Collecting user data without disclosure or tracking without ATT

// Guideline 3.1 - Payments:
//   Selling digital goods outside of Apple's IAP system

// Guideline 1.0 - Objectionable Content:
//   Offensive content, hate speech, graphic violence

The Resolution Center

When your app is rejected, Apple posts the reason in the Resolution Center in App Store Connect. You can reply directly to the reviewer, ask clarifying questions, and provide additional context. If you believe the rejection is incorrect, you can appeal or request a phone call with the App Review team. Resolution Center messages are timestamped — Apple typically responds within 1–2 business days.

// Resolution Center communication tips:

// 1. Read the full rejection message carefully
//    Apple often quotes the specific guideline violated

// 2. Ask clarifying questions if the rejection is vague
//    'Could you clarify which specific screen had the crash?'

// 3. Explain your fix clearly
//    'We have fixed the crash by adding a null check in line 45.
//     The updated build (version 1.0.1) addresses this.'

// 4. Provide a video if the feature is hard to find
//    Attach a screen recording to your reply

Guideline 2.1: App Completeness

Guideline 2.1 rejections mean the reviewer found the app incomplete or non-functional. Common causes include: broken flows the reviewer could not complete, missing test credentials, a feature that works only on specific device models, or a login that fails (perhaps your staging backend is down). Always test the app on a clean device with a fresh account using the exact credentials you provided in the review notes.

// Pre-submission checklist to avoid 2.1:

// 1. Test on a REAL device (not just simulator)
// 2. Create a dedicated review account and TEST IT
//    - Log in fresh (don't use a pre-seeded account)
//    - Complete the sign-up flow from scratch
// 3. Test every tab / navigation path
// 4. Test with a fresh install (no leftover cached state)
// 5. Check that all images, API calls, and links load
// 6. Verify screenshot accuracy matches current app UI

Guideline 5.1: Privacy Violations

Apple enforces privacy guidelines strictly. Guideline 5.1 covers: collecting device data without user consent, using IDFA/device fingerprinting without the ATT (App Tracking Transparency) prompt, missing usage description strings in Info.plist, and not disclosing collected data in the Data Safety section. The ATT framework must be implemented if you track users across apps or websites — calling requestTrackingAuthorization() before any tracking activity.

// App Tracking Transparency (ATT) - required for tracking
import { requestTrackingPermissionsAsync } from 'expo-tracking-transparency';

async function requestTracking() {
  const { status } = await requestTrackingPermissionsAsync();
  if (status === 'granted') {
    // User opted in — enable analytics/ads
    initializeAnalytics();
  } else {
    // User declined — use anonymous/aggregated data only
    initializeAnonymousAnalytics();
  }
}

// Info.plist required:
// NSUserTrackingUsageDescription: 'We use tracking to personalize ads.'

Guideline 3.1: Payment Guidelines

If your app sells digital goods or subscriptions, Apple mandates they go through its In-App Purchase (IAP) system. You cannot link to a web payment flow for digital content that can be used in the app — doing so triggers a Guideline 3.1 rejection. Physical goods (e.g., ordering a pizza), services rendered in-person (e.g., a taxi ride), and business-to-business sales have explicit exemptions. When in doubt, use IAP.

// What requires Apple IAP:
// - Premium features / unlocks
// - Subscriptions to content or services
// - Virtual currency / gems
// - Consumable boosts inside the app

// What does NOT require IAP:
// - Selling physical goods (ecommerce)
// - Services delivered in-person (food delivery, rideshare)
// - B2B enterprise sales
// - Reader apps reading content purchased elsewhere (Reader Rule)
//   e.g., Kindle, Spotify (no in-app upgrade allowed though)

Expedited Review Requests

Apple offers an expedited review process for time-sensitive situations: critical bug fixes, security vulnerabilities discovered in production, or a release tied to a major media event. Submit an expedited review request through the Resolution Center after submitting the build. Provide a business justification — Apple evaluates requests individually and approves a subset. This does not guarantee same-day approval but typically cuts wait time significantly.

// When to request expedited review:
// - Production crash affecting >X% of users
// - Security vulnerability that needs immediate patch
// - Legal deadline (court order, regulation change)
// - Major event launch (Conference release, holiday launch)

// Process:
// App Store Connect > Resolution Center
// > Request Expedited Review
// > Choose: App Update
// > Explain the urgency (2-3 sentences)
// > Submit request

Responding to a Metadata Rejection

Metadata rejections (name, screenshots, description) do not always require a new binary. You can update the metadata and resubmit the same build for review. Fix the specific item called out (e.g., a screenshot showing a feature you removed), update it in App Store Connect, and reply in the Resolution Center explaining what you changed. This can be resolved much faster than issues requiring code changes.

// Metadata rejection workflow:
// 1. Read the specific guideline cited
// 2. Update the metadata in App Store Connect
//    (Screenshots, Description, Keywords, etc.)
// 3. Go to Resolution Center
// 4. Reply with:
//    'We have updated the screenshot for the Home tab to accurately
//     reflect the current app UI. The feature shown (X) is available
//     after sign-in. Please see the updated screenshot attached.'
// 5. Click 'Resubmit for Review' (not a new version submission)

Appealing a Rejection

If you disagree with a rejection, you can formally appeal to the App Review Board. This is appropriate when you believe your app complies with the guidelines and the reviewer made an error. File the appeal through the Resolution Center, citing the specific guideline you believe you comply with and providing evidence. Appeals take longer than just fixing and resubmitting. For borderline cases, consider calling the App Review team — it is a real phone conversation with a reviewer.

// When to appeal vs. fix-and-resubmit:

// Fix and resubmit (faster):
// - Clear violation you can fix in < 1 day
// - Crash reproducible and fixable
// - Missing info you can add easily

// Appeal:
// - You genuinely comply but reviewer misread the app
// - You need a policy exception for your use case
// - Your app is being held to a different standard
//   than similar apps already on the store

// Resolution Center > Reply to Review > Request Appeal

Post-Approval: Phased Release

After approval, instead of releasing to all users immediately, use Phased Release. Apple rolls out the update to a percentage of users over 7 days (1%, 2%, 5%, 10%, 20%, 50%, 100%). You can pause the rollout at any point if crash rates spike. This limits the blast radius of a bug that slipped through testing. Phased release is available for app updates, not first submissions.

// Enable Phased Release in App Store Connect:
// My Apps > Version > Phased Release for Automatic Updates
// Select: Release over 7-day period

// Day 1: 1% of users
// Day 2: 2% of users
// Day 3: 5% of users
// Day 4: 10% of users
// Day 5: 20% of users
// Day 6: 50% of users
// Day 7: 100% of users

// You can manually pause if crash rates rise:
// Version > Phased Release > Pause

Quick Check

Test your understanding of React Native Mobile Development concepts from this lesson.

인터랙티브 레슨에서 답해보세요

Lesson Recap

In this lesson you learned: how the App Store review process works and typical timelines, how to use the Resolution Center to respond to and appeal rejections, and how to avoid the most common rejection reasons (2.1 completeness, 5.1 privacy, 3.1 payments). You also saw how to request expedited review and use Phased Release to limit rollout risk. Next up we cover creating a keystore and signing the Android AAB.

무료로 시작

AI 튜터와 함께 JavaScript을(를) 배우세요 — 무료

브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.

코스
30
레슨
120
무료로 학습 시작전체 코스 보기

자주 묻는 질문

“심사 제출 및 거부에 대응하기” 강의는 무료인가요?

네 — “심사 제출 및 거부에 대응하기” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 React Native Academy 강의 전체를 잠금 해제할 수 있습니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.

“심사 제출 및 거부에 대응하기”에서 뭘 배우나요?

EAS Submit 또는 Transporter로 빌드를 업로드하고 App Store Connect에서 심사용으로 선택하며, 가장 흔한 거부 사유와 해결 방법을 이해합니다. 브라우저에서 직접 실행하는 실습 코드로 React Native Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

React Native Academy을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 React Native Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 4번째 강의입니다.

“심사 제출 및 거부에 대응하기” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 React Native Academy 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 React Native Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. Apple Developer 계정 설정 및 인증서
  2. EAS Build로 서명 구성하기
  3. App Store Connect에서 App Store 메타데이터 준비하기
  4. 심사 제출 및 거부에 대응하기
← React Native Academy(으)로 돌아가기