OtaKitPassing your first App Store and Google Play review
The most common reasons first submissions get rejected, a pre-submission checklist for Capacitor apps, and how OTA updates let you fix post-launch issues without waiting on another review.
Your first submission to the App Store or Google Play is where a lot of projects stall — usually on avoidable things. Review isn't out to get you, but it is consistent about a handful of issues. This guide covers the common rejection reasons, a pre-submission checklist for Capacitor apps, and how over-the-air updates take the pressure off getting everything perfect on day one.
Mental model: get the app approved once, cleanly. After that, most fixes and improvements ship over the air — you rarely wait on review again.
The usual rejection reasons
- Incomplete or broken app. Placeholder screens, dead buttons, obvious bugs. Reviewers open everything.
- Crashes on launch. Test on a real device, on the OS versions you claim to support — not just the simulator.
- Privacy gaps. Missing privacy policy, inaccurate data-safety labels, or a missing iOS privacy manifest.
- Login walls without a demo account. If the app requires sign-in, provide working review credentials.
- Permissions without justification. Every permission needs a clear reason string and an in-app purpose the reviewer can see.
- Payments outside the rules. Digital goods generally must use In-App Purchase / Play Billing.
Pre-submission checklist for Capacitor apps
- Run the release build on a real iOS and Android device, not just simulators.
- Confirm every core flow works offline-to-online and handles network failure gracefully.
- Fill in accurate store metadata, screenshots, and a reachable privacy policy URL.
- Provide demo credentials and any “how to test” notes reviewers need in the review information field.
- Add the iOS privacy manifest and make sure plugins/SDKs are current so their manifests are included.
- Set correct age ratings and permission usage descriptions.
- Verify the app does what the listing says — no more, no less.
How OTA changes the stakes
The reason a first review feels high-stakes is that a native release cycle is slow — a rejection or a post-launch bug means days of waiting. With OTA in place, that's only true for native changes. Once your Capacitor app is approved with an OTA plugin like OtaKit configured, you can fix the web-layer issues that inevitably surface after launch and ship them the same day — no resubmission.
That said, don't use OTA as a crutch to submit an unfinished app. Review expects a complete app; OTA is for iterating on it. See what OTA can and can't change.
Submit a complete, tested app; then let OTA absorb the long tail of post-launch fixes. That combination is what makes shipping on mobile feel fast.
Where to go next
Read the iOS privacy manifest guide and Apple guideline 2.5.2, then get OTA set up with the setup guide.