Amazon Appstore Rejection Reasons and How to Fix Them

Getting your app rejected by Amazon Appstore is frustrating — especially when the rejection email is vague. After analyzing thousands of submissions, here are the 7 most common Amazon Appstore rejection reasons and the exact fixes to get approved on resubmission.

Every rejection reason below includes the exact error message you will see and the specific fix. Bookmark this page — you will need it.

Rejection Overview

1. Missing Privacy Policy

Error: "Your app does not include a privacy policy URL."

Fix: Add a privacy policy URL in two places: your app store listing AND inside the app itself (typically in Settings or About screen). If your app uses ads, analytics, or collects any data whatsoever, Amazon requires this.

You do not need a lawyer. Use a free privacy policy generator, host it on your website, and add the URL to your listing. This is a 5-minute fix that prevents the single most common rejection.

2. App Crashes on Launch

Error: "Your app crashes or becomes unresponsive during testing."

Fix: Amazon tests on real Fire TV and Fire Tablet devices. Common crash causes:

• Missing internet permission when your app needs network access
• Hardcoded screen dimensions that do not match TV resolution
• Third-party SDK initialization failing — check your ad SDK setup
• ProGuard or R8 stripping classes needed at runtime
• Missing LEANBACK_LAUNCHER category in the manifest for Fire TV apps

Always test on a real device or the Amazon Device Farm before submitting. The emulator does not catch everything.

3. Broken D-Pad Navigation (Fire TV Only)

Error: "Your app does not support D-pad navigation."

Fix: Fire TV has no touchscreen. Your app must be fully navigable using only the remote control. Ensure all interactive elements are focusable by adding android:focusable="true" to clickable views. Test every screen with arrow keys only — no touch input, no mouse clicks.

This is the most common Fire TV-specific rejection. See the full Fire TV requirements checklist for everything you need.

4. Incorrect Screenshots

Error: "Screenshots do not accurately represent the app experience."

Fix: Use actual screenshots from the app running on the target device. For Fire TV, screenshots must be 1920x1080 (landscape). For tablets, use tablet-sized screenshots. Never upload phone screenshots for a TV app listing.

FullPublish generates screenshots at the correct dimensions automatically — device-framed and store-ready for each platform.

5. Misleading Metadata

Error: "App title or description contains misleading claims."

Fix: Do not claim features your app does not have. Avoid superlatives like "best" or "fastest" unless you can prove them. Do not reference competitor apps or trademarks in your description or keywords. Keep it factual and specific.

6. Ad SDK Issues

Error: "App displays ads in a way that interferes with navigation."

Fix: Ensure ads do not cover the entire screen without a visible close button. On Fire TV, interstitial ads must be dismissible via the remote control. Do not show ads immediately on app launch — wait at least one user interaction. Ad refresh rate must be minimum 30 seconds.

7. Target SDK Too Low

Error: "App targets an API level below the minimum required."

Fix: Amazon requires targetSdkVersion of at least API 28 (Android 9). Update your build.gradle, test for compatibility, and rebuild.

How to Avoid Rejections Entirely

FullPublish's automated pipeline handles every common rejection point: correct screenshot dimensions, proper metadata formatting, tested APK builds, privacy policy compliance, and all required assets. The platform has processed thousands of successful submissions and knows exactly what Amazon expects.

Learn how app publishing automation prevents these issues, or apply for access to start publishing with confidence.