Digital Agency Bangkok Co., Ltd.

Your dream in digital formats!

Why App Store and Google Play Reject Apps: What to Prepare Before Submitting

App Store and Google Play reject apps for crashes and bugs, incomplete or misleading listings, missing privacy policies and data disclosures, unnecessary permissions, broken sign-in or account deletion, and payment rule violations. Before submitting, test on real devices, complete the privacy details, prepare reviewer access, and check both stores' current guidelines.

A rejection after months of development is frustrating, and most rejections are avoidable. The stores publish their rules, and reviewers check the same things repeatedly. This guide explains the common reasons for rejection and gives a checklist to work through before you press submit. Rules change often, so always check the current guidelines from Apple and Google.

Key takeaways - Most rejections come from bugs, missing information or a mismatch between the listing and the app. - Privacy details, permissions and account deletion are checked closely. - Give reviewers a working demo login and clear notes. - Plan extra time for review and fixes before your launch date. - Read both stores' current guidelines before submitting, because they change.

Why do stores reject apps?

Both stores review apps for quality, safety, privacy and honesty. Apple reviews each submission against its App Review Guidelines. Google Play checks against its Developer Program Policies, using automated and manual review. The details differ, but the underlying themes are similar.

What are the common reasons for rejection?

Area Typical problem How to avoid it
Crashes and bugs The app crashes, freezes or has broken buttons Test on real devices and on several OS versions
Incomplete app Placeholder text, dead links, empty screens Remove test content and check every link
Misleading listing Screenshots or description show features the app does not have Make the listing match the real app
Missing privacy policy No link, or a link that does not work Publish a policy and link it in the listing and in the app
Privacy disclosures Data collection forms do not match what the app does Document what you collect and why, and keep the forms accurate
Excess permissions The app asks for access it does not need Ask only for what a feature requires, and explain why
Sign-in problems Reviewers cannot log in, or a required login option is missing Provide a demo account. On iOS, if you offer third-party logins such as Google or Facebook for the main account, Apple generally requires an equivalent privacy-focused option, such as Sign in with Apple
Account deletion The app lets people create an account but not delete it Offer account deletion inside the app
Payment rules Digital goods or subscriptions sold outside the store's payment system Digital content and features unlocked in the app generally must use the store's in-app purchase system; physical goods and real-world services can use other payment methods. Rules vary by country, so check each store's current payment policy
Minimal functionality The app is little more than a wrapped website Add real app value, such as useful features
Content and legal Restricted content, copied material, unclear ownership Check content policies and your rights

What should you prepare before submitting?

Accounts - A developer account for each store, in the right name. Apple's Developer Program has an annual fee, and Google Play charges a one-time registration fee. Both verify the developer's identity, and organisation accounts need company details. - On Google Play, new personal developer accounts must run a closed test with a set number of testers for a set period before they can publish. An organisation account avoids this step, so register in the business's name if you can. - Contact details that reviewers can reach.

The app - A tested, stable build with no placeholder content. - Clear in-app navigation and working links. - Testing on real phones, not only simulators. - Builds that meet the stores' current technical requirements, such as Google Play's minimum target Android version and Apple's current SDK. Both raise these regularly, usually once a year.

Privacy and data - A published privacy policy that matches what the app does. - Accurate answers in the stores' privacy and data safety forms. - A clear explanation for every permission the app requests. - Account deletion inside the app, if people can create accounts. - Consent steps that suit Thai privacy rules and your audience.

Listing - Accurate title, description and keywords. - Screenshots that show the real app. - An age rating questionnaire answered honestly. - A support URL and contact email.

Reviewer access - A working demo account with sample data. - Notes explaining how to reach features that need special conditions, such as a location, a booking or a payment.

What if the app needs a login or payment to see its features?

Reviewers cannot guess how to use your app. Provide a demo login, test data and short notes that explain any steps. If a feature needs payment, explain how to test it without charging a real card. Missing reviewer access is one of the most common avoidable causes of delay.

How long does review take?

Apple says most submissions are reviewed within a day or two. Google Play reviews can take several days, and longer for new apps or accounts. Incomplete submissions take longer. Plan extra time before any launch date, and avoid scheduling a campaign for the same day you submit. For a view of the whole development timeline, see how long mobile app development takes in Thailand.

What should you do if the app is rejected?

  1. Read the rejection message carefully and note the guideline or policy named.
  2. Compare it with what the app does and what the listing says.
  3. Fix the real issue instead of reworking only the explanation.
  4. Reply through the store's review channel if you need clarification, and be specific and polite.
  5. Resubmit with notes on what you changed.
  6. Appeal only if you believe the reviewer made a mistake, and explain why with evidence.

Avoid resubmitting the same build unchanged, because it is likely to be rejected again.

What should you check after approval?

  • Install the live version and test it on a real device.
  • Check that the listing displays correctly in both languages you support.
  • Monitor crash reports and reviews.
  • Keep the privacy forms current when you add features or data collection.
  • Plan updates for new operating system versions.

For an example of a project delivered to both stores, see our Yuzanar Land real estate mobile apps case study.

What mistakes should you avoid?

  • Submitting without testing on real devices
  • Leaving placeholder text or broken links in the app
  • A listing that promises more than the app does
  • Collecting data without disclosing it
  • Requesting permissions the app does not need
  • No demo account for reviewers
  • Planning a launch date with no buffer for review

How does DAB handle this?

DAB provides mobile app development and has 18+ years of experience in digital marketing and web development in Bangkok. Our mobile app development service includes preparing apps for submission so the store requirements are planned from the start.

Preparing to launch an app?

If you are planning an app or have had one rejected, contact DAB through LINE or our contact page. Learn more about our mobile app development service.

FAQ

Why was my app rejected for "minimum functionality"?

The reviewer felt the app offers too little beyond a website. Add features that make real use of the app format, such as notifications, accounts or device features that matter to users.

Do I need a privacy policy for my app?

Yes. Both stores expect a privacy policy that matches what your app does. Link it in the listing and inside the app.

Can I appeal a rejection?

Yes, through the store's review process. Appeal only when you believe the decision was wrong, and explain clearly with evidence. If the reviewer found a real issue, fix it instead.

Why does the store ask for a demo login?

Reviewers must test features behind a login. Without access they cannot review, and the app may be rejected or delayed.

Do the rules change?

Yes, often. Always check the current App Review Guidelines and Google Play policies before you submit.

LineWhatsapp