Ir al contenido

Rejection codes

A store rejection arrives as a code and a paragraph of the store's own prose. This is what each one means and what to change. A code we have not seen before still reaches your inbox with a usable answer and a reviewer attached.

2.1 — App completeness

Apple App Store

The reviewer could not get into the app or hit something that did not work. Nearly always a sign-in they could not pass, or a feature that needs data the demo account has none of.

  1. Check the demo account in the review notes still works, and that it is not rate-limited or expired.
  2. Sign in with it yourself on a clean device and walk the main path end to end.
  3. If part of the app needs data to make sense, seed the demo account with some.
  4. Reply in Resolution Center with the working credentials rather than resubmitting silently.

Fixable without a new build. Usually about 2 hours of work.

4.2.6 — Template or app-generation service

Apple App Store

Apple believes the app was produced from a template and submitted by the service that made it, rather than by you. This is the rule that decides how Retoxy works: your App Store account is yours, and the app is submitted from it.

  1. Confirm the submission came from your own Apple Developer account, in your own legal name.
  2. Make sure the app's name, icon, screenshots and description are yours and not a generic set.
  3. Remove any text or links that advertise the tool the app was built with.
  4. If the app is one of several similar apps for different businesses, each needs its own account; say so in the reply.

Fixable without a new build. Usually about 8 hours of work.

4.3 — Spam or duplicate

Apple App Store

Apple thinks this app is too close to another already on the store, often another of your own.

  1. Point out in the reply what this app does that the others do not.
  2. If you have several near-identical apps, consider one app with the differences inside it.
  3. Rewrite the description so it reads for a user rather than for search.

Fixable without a new build. Usually about 6 hours of work.

5.1.1 — Data collection and storage

Apple App Store

The app asks for data it does not need to work, or asks before explaining why, or requires an account for something that does not need one.

  1. Delay each permission prompt until the moment the feature is used, and show a sentence explaining why first.
  2. Make any sign-in optional for the parts of the app that do not need it.
  3. Check the privacy labels match what the app actually sends.

Needs a new build. Usually about 12 hours of work.

5.1.5 — Location services

Apple App Store

The app uses location without the user being able to see why, or keeps using it in the background without saying so.

  1. Add a purpose string that names the feature, not the permission.
  2. Drop to when-in-use unless background location is genuinely core.
  3. Show a visible indicator while location is being used in the background.

Needs a new build. Usually about 10 hours of work.

3.1.1 — In-app purchase required

Apple App Store

The app unlocks digital content through a payment that is not Apple's in-app purchase.

  1. Use in-app purchase for digital content consumed inside the app.
  2. Remove buttons and links that send a user out to pay, unless your country and category allow them.
  3. Retoxy's revenue split applies to payments we process; store billing is settled by the store, and your plan reflects that.

Needs a new build. Usually about 24 hours of work.

POLICY_DECEPTIVE_BEHAVIOUR — Deceptive behaviour

Google Play

What the listing promises and what the app does do not match, or the app asks for a permission its description never mentions.

  1. Line the description up against what the app actually does, feature by feature.
  2. Name every sensitive permission in the description and say what it is for.
  3. Remove any claim you cannot demonstrate in the app.

Fixable without a new build. Usually about 4 hours of work.

POLICY_PERMISSIONS — Permissions and APIs that access sensitive information

Google Play

The app requests a restricted permission without an approved use case or a completed declaration.

  1. Check whether the feature can be built with a narrower API: the photo picker instead of all-files access, a share sheet instead of SMS reading.
  2. If the permission is genuinely core, complete the declaration form and record the use case.
  3. Attach a short screen recording showing the user-facing feature that needs it.

Needs a new build. Usually about 16 hours of work.

POLICY_DATA_SAFETY — Data safety form mismatch

Google Play

Google compared the form against the app's traffic and found data leaving that the form does not declare. An SDK is usually the cause.

  1. List every third-party SDK in the build and what each one sends.
  2. Update the data-safety form to match, including data collected by SDKs you did not write.
  3. Remove any SDK you cannot account for.

Fixable without a new build. Usually about 6 hours of work.

POLICY_TARGET_API — Target API level

Google Play

The build targets an Android version older than Play now accepts.

  1. Raise targetSdkVersion to the current floor and read the behaviour changes for each version you skip.
  2. Test the permission prompts and background work, which are what usually break.
  3. Upload a new build; the listing itself needs no change.

Needs a new build. Usually about 20 hours of work.

POLICY_FAMILIES — Families policy

Google Play

The app is aimed at or appeals to children and does not meet the extra rules for that audience.

  1. Set the target age group honestly in the content rating questionnaire.
  2. Remove behavioural advertising and any SDK that profiles users.
  3. Add a neutral age screen if the app is for a mixed audience.

Needs a new build. Usually about 24 hours of work.

METADATA_SCREENSHOTS — Screenshots do not show the app

Any store

The screenshots are mock-ups, marketing frames or a different app rather than the app's own screens.

  1. Take screenshots from the build being submitted, at the required sizes.
  2. Keep added text to a caption; the screen itself must be visible.
  3. Do not show a device frame the store does not sell.

Fixable without a new build. Usually about 3 hours of work.

METADATA_PRIVACY_POLICY_UNREACHABLE — Privacy policy unreachable

Any store

The reviewer could not open the privacy policy URL: it 404s, needs a login, or is behind a region block.

  1. Open the URL in a private window from outside your own network.
  2. Remove any login, cookie wall or geo-restriction in front of it.
  3. Make sure the policy names your legal entity and the app by name.

Fixable without a new build. Usually about 1 hours of work.