Privacy policy
No privacy policy URL has been given. Every store on your list requires one, whether or not the app collects data.
Fix: Add a publicly reachable https:// privacy policy URL that does not sit behind a login.
These run in the wizard before anything is submitted. Each one is a rejection we have seen a store issue. A failure blocks the submission; a warning is a judgement call and lets you proceed.
The current Google Play target API floor recorded here is API 35, read on 2026-11-15, and it has not yet been confirmed by a person against Play's own page. Google raises it annually. Treat the figure as indicative until that check is recorded.
No privacy policy URL has been given. Every store on your list requires one, whether or not the app collects data.
Fix: Add a publicly reachable https:// privacy policy URL that does not sit behind a login.
No support email or support URL. Stores show this on the listing and require at least one.
Fix: Add a support email address that a person actually reads, or a support page.
The build targets API 28. Google Play requires at least API 35 for new apps and updates.
Fix: Raise targetSdkVersion to 35 or higher, test on that API level, and upload a new build.
The build requests 16 permissions that stores scrutinise: android.permission.READ_SMS, android.permission.RECEIVE_SMS, android.permission.READ_CALL_LOG, android.permission.WRITE_CALL_LOG, android.permission.ACCESS_BACKGROUND_LOCATION, android.permission.QUERY_ALL_PACKAGES, android.permission.MANAGE_EXTERNAL_STORAGE, android.permission.REQUEST_INSTALL_PACKAGES, android.permission.SYSTEM_ALERT_WINDOW, android.permission.RECORD_AUDIO, android.permission.CAMERA, android.permission.READ_CONTACTS, android.permission.POST_NOTIFICATIONS, android.permission.BLUETOOTH_SCAN, android.permission.READ_MEDIA_IMAGES, android.permission.USE_EXACT_ALARM.
Fix: android.permission.READ_SMS: SMS access is restricted to a default SMS handler and needs a declaration form. android.permission.RECEIVE_SMS: SMS access is restricted to a default SMS handler and needs a declaration form. android.permission.READ_CALL_LOG: Call log access needs an approved use case and a declaration form. android.permission.WRITE_CALL_LOG: Call log access needs an approved use case and a declaration form. android.permission.ACCESS_BACKGROUND_LOCATION: Background location needs a declaration, a video walkthrough and a prominent-disclosure screen. android.permission.QUERY_ALL_PACKAGES: Listing every installed app needs an approved use case. android.permission.MANAGE_EXTERNAL_STORAGE: All-files access needs an approved use case; most apps must use scoped storage instead. android.permission.REQUEST_INSTALL_PACKAGES: Installing other packages needs a declared, core use case. android.permission.SYSTEM_ALERT_WINDOW: Drawing over other apps is restricted and is a common rejection. android.permission.RECORD_AUDIO: Microphone access needs a prominent disclosure and a privacy-policy entry. android.permission.CAMERA: Camera access needs a privacy-policy entry describing what is done with the images. android.permission.READ_CONTACTS: Contacts access needs a prominent disclosure and must not be used for discovery without consent. android.permission.POST_NOTIFICATIONS: Notifications must be requested in context, not on first launch. android.permission.BLUETOOTH_SCAN: Nearby-device scanning must declare whether it derives location. android.permission.READ_MEDIA_IMAGES: Media access should use the photo picker where possible. android.permission.USE_EXACT_ALARM: Exact alarms need a user-facing justification.
android.permission.READ_SMS, android.permission.RECEIVE_SMS, android.permission.READ_CALL_LOG, android.permission.ACCESS_BACKGROUND_LOCATION requires a signed declaration form, and the data-safety section has not been completed.
Fix: Complete the data-safety declaration and the permission declaration form before submitting, or remove the permission.
The age-rating questionnaire has not been completed. No store will accept the listing without it.
Fix: Answer the age-rating questionnaire in the wizard; it is the same set of answers for every store.
The data-safety form has not been filled in. Google Play blocks submission without it and Apple requires the equivalent privacy nutrition labels.
Fix: Complete the data-safety section, listing every data type the app collects and whether it is shared.
The app requires an account but offers no way to delete it. Both Google Play and Apple require in-app deletion and a web route.
Fix: Add account deletion inside the app and publish a web page that does the same.
The app needs an account to use, and no working demo credentials were supplied. This is the single most common rejection.
Fix: Supply a demo account that stays valid, or a sign-in bypass code, in the review notes.
The app shows ads but the listing does not declare it.
Fix: Tick the contains-ads declaration; stores check it and treat a mismatch as a misrepresentation.
The app sells digital goods through a payment provider other than the store's own billing. Rules on this differ by store and by country and have been changing.
Fix: Confirm per store whether external purchase links are permitted in your target countries before submitting. Retoxy's revenue split applies to payments we process, not to store billing.
No listing text has been written.
Fix: Write at least the default-language title, short description and full description.
No app icon has been uploaded.
Fix: Upload a square icon at the largest size you have; the wizard produces the per-store sizes.
Google Play needs at least 2 screenshots; 0 are uploaded.
Fix: Upload 2 more screenshots at that store's required dimensions.
Google Play requires a 1024x500 feature graphic.
Fix: Upload a feature graphic; the wizard can generate one from the icon and title as a starting point.
Apple requires an export-compliance answer about encryption before a build can be submitted.
Fix: Answer the encryption question in the wizard; most apps using only https qualify for the exemption.
"nonsense" is not a dotted version. Stores accept it, but your release tracker and your users will both read it.
Fix: Use a dotted version such as 1.4.0.
The build's version code is not a positive integer, so it cannot be an update of anything.
Fix: Set a version code higher than the last submitted build.
| Permission | What the store will want |
|---|---|
| android.permission.READ_SMS | SMS access is restricted to a default SMS handler and needs a declaration form. |
| android.permission.RECEIVE_SMS | SMS access is restricted to a default SMS handler and needs a declaration form. |
| android.permission.READ_CALL_LOG | Call log access needs an approved use case and a declaration form. |
| android.permission.WRITE_CALL_LOG | Call log access needs an approved use case and a declaration form. |
| android.permission.ACCESS_BACKGROUND_LOCATION | Background location needs a declaration, a video walkthrough and a prominent-disclosure screen. |
| android.permission.QUERY_ALL_PACKAGES | Listing every installed app needs an approved use case. |
| android.permission.MANAGE_EXTERNAL_STORAGE | All-files access needs an approved use case; most apps must use scoped storage instead. |
| android.permission.REQUEST_INSTALL_PACKAGES | Installing other packages needs a declared, core use case. |
| android.permission.SYSTEM_ALERT_WINDOW | Drawing over other apps is restricted and is a common rejection. |
| android.permission.RECORD_AUDIO | Microphone access needs a prominent disclosure and a privacy-policy entry. |
| android.permission.CAMERA | Camera access needs a privacy-policy entry describing what is done with the images. |
| android.permission.READ_CONTACTS | Contacts access needs a prominent disclosure and must not be used for discovery without consent. |
| android.permission.POST_NOTIFICATIONS | Notifications must be requested in context, not on first launch. |
| android.permission.BLUETOOTH_SCAN | Nearby-device scanning must declare whether it derives location. |
| android.permission.READ_MEDIA_IMAGES | Media access should use the photo picker where possible. |
| android.permission.USE_EXACT_ALARM | Exact alarms need a user-facing justification. |
| Store | Title | Short description | Full description | Screenshots |
|---|---|---|---|---|
| Google Play | 30 | 80 | 4000 | 2 |
| Apple App Store | 30 | 170 | 4000 | 3 |
| Amazon Appstore | 50 | 120 | 4000 | 3 |
| Microsoft Store | 256 | 200 | 10000 | 1 |
| Samsung Galaxy Store | 50 | 80 | 4000 | 4 |
| Huawei AppGallery | 64 | 80 | 8000 | 3 |
| Meta Horizon Store | 50 | 100 | 4000 | 5 |
| AppBona | 60 | 120 | 8000 | 2 |
| Web / PWA | 60 | 120 | 8000 | 1 |
| Direct download | 60 | 120 | 8000 | 1 |