Short answer
When Apple or Google rejects your app, the message is short but the fix often touches code, metadata and privacy declarations at once. We read the rejection precisely, fix what the reviewer actually objected to and resubmit with clear review notes, working in your own developer accounts.
On this page
A rejection is a specification, not a verdict
Rejection messages from App Review and Google Play are terse. They cite a guideline number, sometimes attach a screenshot and leave the rest to you. Teams under launch pressure tend to react in one of two ways: change something at random and resubmit, or argue with the reviewer. Both waste review cycles.
We approach a rejection as a precise specification of what must change. The guideline cited, the device and OS version used, the screenshot and the exact wording together usually tell you what the reviewer saw. Our job is to reproduce that, fix it properly and explain the fix in a way the next reviewer can verify quickly.
The rejections we see most
Guideline 4.2, Minimum Functionality (Apple). The reviewer considers the app too thin, a repackaged website or not "app-like" enough. Common with wrapped web apps and early prototypes. The fix is genuine native value: push notifications for meaningful events, offline behaviour, device features that serve the use case, and navigation that does not look like a browser.
Guideline 2.1, App Completeness. Crashes, broken links, placeholder content or a login the reviewer could not get past. Usually fixed with stability work and proper demo credentials in the review notes.
Guideline 5.1, Privacy. Missing account deletion, unclear purpose strings for camera or location access, privacy labels that do not match what the app does, or data collected before consent.
Metadata rejections. Screenshots that do not show the app in use, keywords naming competitors, descriptions promising features that are not there.
Google Play policy issues. Data safety form mismatches, missing privacy policy links, target API level requirements, permissions that need declarations, and content policy flags.
Our process after a rejection
- Read and reproduce. We analyse the rejection text and attachments, install the exact build on comparable devices and reproduce the issue.
- Root cause. We separate the cited symptom from the actual cause. A 4.2 rejection is sometimes really a stability or login problem that left the reviewer seeing an empty shell.
- Fix. Code, configuration, metadata or privacy declarations, whatever the cause requires. For web-based apps, adding native capabilities through WebViewGold, such as push notifications, offline support and native APIs, is often the decisive change for a 4.2 finding.
- Review notes. We write factual notes: what changed, where to find it, how to log in, which features require specific conditions.
- Resubmit and respond. We submit from your account, reply to follow-up questions in the resolution centre or Play Console and, where warranted, use the formal appeal routes.
For the submission work we rely on appsubmitter.io, which combines AI-assisted preparation with human submission experts, works inside your own developer accounts and covers store listings, CI/CD and help with rejections.
What we decide and what you decide
We own the diagnosis, the fixes we agree on, the review communication and the resubmission. You keep control over product decisions the fix may require: whether to add a feature, remove a payment flow, change the business model to fit store rules or accept a narrower set of countries. Appeals and statements to Apple or Google on behalf of your company are sent with your approval. If a rejection concerns legal content, such as your privacy policy or terms, we flag the gap; your legal team owns the wording.
Avoiding the next rejection
After approval we leave behind a short pre-submission checklist tailored to your app, demo credentials that do not expire, and a pipeline that builds release versions consistently. Many repeat rejections come from changes that undo earlier fixes, so we document which parts of the app exist specifically because of a past review finding.
This service is part of prototype to production. If the rejection exposed deeper quality problems in the codebase, our AI Code Engineering team can address them.
What to expect
A clear explanation of why the app was rejected, a fix that addresses the cause rather than the wording, and a resubmission that gives the reviewer everything needed to approve. Some rejections take more than one round, especially policy questions; we keep you informed at every step.
If your app was built with an AI coding agent, see our Codex App Store launch service. For progressive web apps, read publishing a PWA in the App Store.
FAQ
What does Guideline 4.2 Minimum Functionality mean?
Apple expects apps to provide features, content and an experience beyond a repackaged website. Apps that feel like a browser window or offer very little are rejected under 4.2. Adding real native value and polishing navigation usually resolves it.
Should we appeal or fix?
Fix in most cases. Appeals make sense when the reviewer misunderstood the app, and good review notes often prevent that misunderstanding in the first place.
Can you help with Google Play policy rejections too?
Yes. We handle data safety, permissions, target API level and policy declaration issues in the Play Console.
Do you need access to our developer accounts?
Yes, with a role you grant and can revoke. The apps always stay in your accounts.