How do I fix an App Store rejection?

First, identify the specific guideline violation from your rejection notice in App Store Connect. Common fixes include: adding a privacy policy URL, implementing Sign in with Apple for apps with third-party login, using In-App Purchase for digital goods, and ensuring screenshots accurately represent your app. Once fixed, submit a new build—replying in the Resolution Center alone does not trigger a new review.

Why was my app rejected from Google Play?

Google Play rejections typically fall into these categories: Data Safety form issues (incomplete or inaccurate declarations), sensitive permissions without core functionality justification (SMS, Call Log, Location), policy violations (deceptive behavior, misrepresentation), and technical issues (target SDK too old, 16KB page alignment for new devices). Check the Policy Center in Play Console for the specific violation and required remediation steps.

How long does an app review appeal take?

Apple typically responds to appeals within 24-72 hours for standard cases, though complex escalations can take up to a week. Google Play appeals usually receive a response within 3-5 business days. You get one appeal per rejected build, so include all relevant evidence (screenshots, demo videos, compliance documentation) in your initial submission. For iOS, you can also request a live App Review Appointment via Webex if written appeals fail.

Can I resubmit while an appeal is pending?

Yes, you can submit a new build while an appeal is pending on both platforms. This is often the faster path—fix the reported issue and submit an updated binary rather than waiting for the appeal outcome. If your appeal succeeds but you've already submitted a fixed version, the newer build will be reviewed. For metadata-only rejections (screenshots, description, keywords), you can update these directly without uploading a new binary.

What are the most common App Store rejection reasons?

Based on analysis of verified rejections: iOS top issues are Missing Privacy Policy (9.9%), Placeholder Content (7.8%), Misleading Metadata (4.6%), and Sign in with Apple (3.2%). For Google Play, the leaders are Data Safety Issues (11%), Sensitive Permissions (7.2%), and Foreground Service Type (3.2%). Privacy-related violations dominate both platforms, accounting for roughly 20% of all rejections combined.

Back to Rejection Hub

Quick Fix for Guideline 5.1.2

Add NSUserTrackingUsageDescription to Info.plist and call requestTrackingAuthorization() before accessing IDFA. The prompt must clearly explain why you need to track the user.

Guideline 5.1.2

App Tracking Transparency (ATT)

Your app is accessing the IDFA (Identifier for Advertisers) or tracking user activity across other apps/websites without requesting explicit permission via the ATT prompt.

AI-Friendly Summary

To resolve a Guideline 5.1.2 rejection, developers must ensure Apps must get the user's permission before tracking their data across apps or websites owned by other companies. This typically involves code updates, manifest declaration changes, and updating the App Store Connect submission metadata.

Recommended Fix Steps

Add the `NSUserTrackingUsageDescription` key to your Info.plist.

Import the `AppTrackingTransparency` framework.

Call `requestTrackingAuthorization(completionHandler:)` before accessing tracking data.

Ensure the permission prompt explains exactly WHY you need to track.

Implementation Example

Fix Implementation

import { requestTrackingAuthorization } from 'expo-tracking-transparency';

const { status } = await requestTrackingAuthorization();
if (status === 'granted') {
  // Safe to use IDFA
}