App Review Help

App Store and Google Play Rejection Fixes

Tepia fixes App Store and Google Play rejections by reading the cited guideline, correcting the build, metadata or policy forms, and replying to reviewers with evidence. Common causes include Guideline 2.1 app completeness, 4.2 minimum functionality and 5.1.1 data collection, and Tepia aims to clear each rejection in a single resubmission.

The essentials at a glance

A rejection notice is specific once you know how to read it, and the fastest way back into the store is to answer exactly what the reviewer asked.

dream-app

Guideline Fluent

Tepia maps each rejection to the exact App Review Guideline or Google Play policy cited, so the fix targets the real issue, not a guess.

Read: How to Launch an App on the App Store and Google Play
connect-audience

Policy Forms

Privacy nutrition labels, the Data safety form and permission declarations are checked against what the app and its SDKs truly collect.

Read: App Rescue: Taking Over a Struggling App
smart-product

Reviewer Replies

Tepia drafts clear replies with screenshots, demo accounts and video, since many rejections clear once a reviewer can see the feature work.

Read: Mobile App Release Management and Continuous Delivery
optimize-ecommerce

Prevention Checks

Before each release Tepia runs a prelaunch checklist covering crashes, login access, account deletion, purchases and metadata accuracy.

The numbers matter.

Review figures Tepia keeps in view when an app is stuck in App Review.

40%

Guideline 2.1 Issues

Apple says over 40 percent of unresolved App Review issues fall under guideline 2.1, App Completeness, like crashes.

4.5

Average App Rating

Tepia clients report apps averaging 4.5 stars on the App Store and Google Play, once they clear review and reach users.

90%

Reviewed In 48 Hours

Apple states App Review typically reviews 90 percent of submissions in under 48 hours and at least half within 24 hours.

Why apps get rejected

Apple reviews every submission against its App Review Guidelines, and Google Play combines automated checks with human review against its Developer Program Policies. Rejections usually fall into one of four buckets, and Tepia starts by placing yours in the right one:

  • The build: crashes, broken links, placeholder content or features the reviewer could not reach.
  • The business model: digital content or subscriptions sold outside the stores’ billing systems where the rules require in app purchase.
  • Privacy and data: permissions without a clear purpose, missing account deletion, or privacy labels that do not match the SDKs inside the app.
  • The listing: screenshots, descriptions or names that misrepresent what the app does.

A rejection is not a verdict on the app. It is a list of specific objections, and the reply matters as much as the fix. Tepia treats each notice like a support ticket with a clear owner, a code or content change and a written response to the reviewer. Tepia also checks whether the same problem exists on the other store, because an issue Apple flags today often resurfaces as a Google Play policy notice a few weeks later.

Common App Store rejections and how Tepia resolves them

Guideline What the reviewer usually means How Tepia resolves it
2.1 App Completeness The app crashed, a feature was unreachable or the demo login failed Fix the defect, supply a working demo account and write review notes that point to each feature
2.3 Accurate Metadata Screenshots or the description promise something the app does not show Rewrite metadata and capture screenshots from the actual build
3.1.1 In App Purchase Digital goods or subscriptions are sold through an outside payment flow Move digital purchases to StoreKit, or show the purchase is for physical goods or services used outside the app
4.2 Minimum Functionality The app feels like a website in a wrapper Add native value such as offline use, push, device features or deeper account tools
4.3 Spam The app duplicates another app, often one built from a template Differentiate the product or consolidate several apps into one
5.1.1 Data Collection and Storage Unneeded permissions, forced sign up for non account features, or no in app account deletion Trim permissions, add purpose strings and build account deletion

Guideline 4.2 catches many businesses that wrapped their website in a shell. Fixing it properly means building real app features, and our native app vs progressive web app comparison helps you decide which route fits before you resubmit.

Google Play policy issues work differently

Google Play problems often arrive as policy notices in Play Console rather than a single reviewer message, and some carry deadlines. Tepia handles the ones that most often block updates:

  • Data safety form: it must match everything the app and its SDKs collect and share, including analytics and advertising libraries you may have forgotten about.
  • Sensitive permissions: background location, SMS, call log and all files access need declarations and a core feature that genuinely requires them.
  • Target API level: new apps and updates must target a recent Android API level, so an app left untouched for a year or two can suddenly be unable to ship updates.
  • Account deletion: apps that let users create accounts must offer deletion inside the app and through a web link.
  • Families policy: apps aimed at children face stricter rules on ads, SDKs and data collection.

When a decision looks wrong, Tepia files an appeal through Play Console with the evidence attached. On the Apple side, we escalate to the App Review Board when a reply in App Store Connect does not settle it. Appeals work best when they cite the policy language and show the feature working in a short screen recording.

How Tepia approaches App Store and Google Play rejections

Even a single rejection runs through a compact version of Tepia’s six phases, led by a US based project manager.

  1. Discovery: a system investigation of the build, the SDK inventory and the store listings, plus a call with your team about the rejection history. Deliverables are an Investigation Summary covering each cited issue, an Interview Summary and User Stories for any feature that must change.
  2. Design: wireframes for new screens the fix requires, such as account deletion, permission explainers or a native purchase flow.
  3. Development and Testing: code and metadata fixes, then functional and user acceptance testing in TestFlight and Google Play internal testing that mirrors what a reviewer will do.
  4. Training: a short session for your team on review notes, demo accounts and what triggers closer review.
  5. Launch: resubmission with a written reply, monitoring of review status and a staged release once approved.
  6. Support: quick response if a later update is flagged, plus tracking of upcoming policy deadlines on both stores.

Small fixes can go back to review quickly. Larger changes, such as replacing a payment flow, follow the usual development and QA window of 2 to 6 months. See our process for the phase detail.

Preventing the next rejection

Most rejections are preventable with a disciplined release routine. Tepia builds these checks into every submission:

  • A demo account with sample data that never expires, listed in the review notes.
  • Review notes that explain any feature gated behind hardware, location or a paid tier.
  • An SDK inventory reconciled with Apple privacy labels, privacy manifests and the Google Play Data safety form.
  • Account deletion, restore purchases and a privacy focused login option where Guideline 4.8 requires one, tested on each build.
  • Screenshots generated from the current release rather than old mockups.

For apps with frequent releases, our mobile app release management service automates much of this, and our guide on launching on the App Store and Google Play covers first submissions. If you are stuck in review today, contact Tepia with the rejection text, or see apps Tepia has shipped.

Frequently asked questions

Our app was rejected by Apple. Who can help fix it?
Tepia fixes App Store rejections by mapping the notice to the cited guideline, correcting the build or metadata, and replying in App Store Connect with screenshots and a working demo account. If needed, Tepia escalates to the App Review Board.
What does Guideline 4.2 Minimum Functionality mean?
It means Apple sees the app as too thin, often a website in a wrapper. Tepia resolves it by adding real native value such as offline access, push notifications, device features or account tools a browser cannot match.
Why does Apple reject apps under Guideline 2.1?
Guideline 2.1 covers app completeness: crashes, broken links, placeholder content or a demo login that failed during review. Tepia fixes the defect, supplies a durable demo account and writes review notes that walk the reviewer to each feature.
Google Play says our app does not meet the target API level. What do we do?
Tepia updates the app to target a current Android API level, adjusts code for behavior changes such as notification and background limits, and tests on recent devices before resubmitting. Waiting can block updates entirely, so it is worth handling early.
Do we have to add account deletion to our app?
If users can create an account in the app, yes, on both stores. Tepia builds in app account deletion with the matching backend cleanup and adds the web deletion link Google Play requires.

What Our Customers Say.

A paragraph or two with information on your product/service or describes a problem your product/service is designed to solve.

Jascotina

CEO

“They customized the website’s backend to my business' specific needs and I am absolutely thrilled with the result.”

Water Saver Solutions

Senior Project Manager

"Tepia Co was always willing to go the extra mile for us."

Onward Engineering

VP & Operations Manager

"There are no hidden things, there are no surprises. We know what's going on."

Get your app approved and back in stores