Field notes on shipping apps that pass.
Store rules, privacy manifests, SDK risk, and how to stay ahead of all three.
Apple rejects more before publication; Google flags more after it. What that difference means for how you prepare a release.
Read the full postApple rejects apps that can rewrite their own behaviour after approval. What triggers a 2.5.2 rejection, and how to clear it.
Read moreApple parks your build in 'Missing Compliance' until you answer the encryption question. Here is what ITSAppUsesNonExemptEncryption does and what to set before you submit.
Read moreIf your app touches the IDFA or bundles an ad SDK, Apple expects an ATT prompt. Miss NSUserTrackingUsageDescription or the prompt and Guideline 5.1.2 sends it back. What to check in the binary.
Read moreSell digital goods through anything but Apple's In-App Purchase and Guideline 3.1.1 rejects you. The rules shifted with external-link entitlements and the DMA. What still triggers a rejection, and the signals in your binary.
Read moreYour App Privacy label is only as accurate as the SDKs in your build. When the data your binary collects doesn't match what you declared, Apple can reject under 5.1.1. How to check before you submit.
Read moreGuideline 5.1.1 is the most common privacy rejection. The usual causes are missing purpose strings, unused permissions, forced sign-in, or no account deletion. Here is how to fix it before you submit.
Read moreApple reviews most submissions within a day, but a rejection sends you back into the queue. Here is what affects App Store review time in 2026 and how to avoid the re-review loop.
Read moreGoogle Play's 2026 Health and Fitness update added high-sensitivity Health Connect types and a required Health apps declaration form. Here is what changed and how to prepare your Android build.
Read moreGoogle Play's April 15, 2026 update reshaped contacts, location, and foreground-service permissions, and dropped geofencing as an approved use case. Here is each change and the fix.
Read moreGet early access and be first to run all 137 checks on your own build when the doors open.
Your build is deleted the moment the scan finishes. Findings stay for your retention window. EU infrastructure, EU vendors, no AI training on your code.