Drop your .ipa and see what App Review will flag: a missing privacy manifest, empty permission strings, a development-signed build, an outdated SDK. Every finding comes with the Apple rule it comes from.
An .ipa is a zip of everything in your app. The checks only need a few small parts of it, so your browser takes those out and leaves the rest on your machine. Scroll to watch it happen.
These are the build problems that get apps rejected or bounced at upload. Each check reads the actual files in your build.
OFFICIALStated in Apple's documentation or guidelines. Linked to the exact page.
COMMUNITY_HEURISTICWidely reported by developers but not written down by Apple. Shown as a warning, never as a rule.
NOT_PUBLICLY_VERIFIABLEFolklore. Listed for completeness, and it can never fail your build.
A scan reads your build. Plenty of rejections come from things that aren't in it: a login wall in front of features that don't need an account, a missing demo account, account deletion that's really a support ticket, social login without Sign in with Apple, subscriptions without terms, wording in your description. The full review checks those too, instantly.
Fix the blockers it finds. Many apps need nothing more.
Yes or no, about your App Store Connect setup, plus your App Store description. About two minutes.
Instantly, on screen: every issue ordered by rejection risk, with the guideline behind it and how to fix it. Save it as a PDF.
The scan is free forever. The full review and rejection rescue are automated and instant.
No. Your browser opens the .ipa and keeps only Info.plist, privacy manifests and the headers of each binary (linked libraries, symbol names, SDK version, signing entitlements). Compiled code, images and assets stay on your machine. The trimmed file is scanned and not stored.
No, and nobody can promise that. Only Apple approves apps. The scan catches problems that can be detected in a build. Many rejections come from App Store Connect setup, design or business rules instead, which is what the full review covers.
No, it's automated, which is why it's instant. Clear rules check your build and your answers against Apple's published App Review Guidelines, and AI writes the explanations and your reply to App Review using only those guidelines. If the AI is busy, you get the built-in explanation instead.
A report on screen, right away: every issue found across your build, your App Store Connect setup and your description, why it matters, the guideline behind it, and how to fix it, ordered by risk. A rejection rescue adds what Apple's message means, the steps to fix it and a reply you can paste. Save either as a PDF.
Tell us what it missed at the email below and we'll improve the checks. While reviews are free during the beta there's nothing to refund; once they're paid, you get your money back if it didn't help.
App-roved is built by Priyanshu Bhati. The scanning engine is open source, so you can read exactly what it checks: github.com/Priyanshu-bhati23/app-roved.
No. App-roved is independent. App Store and App Review are trademarks of Apple Inc.