You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
1. Apple upload time enforcement (the modern first wall). Advanced 2026
#1015
These are checked when you upload the binary, before a human reviewer ever opens the app. Getting them wrong means the build is rejected or stuck and never reaches review.
Item
What it is
What triggers the block
Fix
Privacy Manifest, PrivacyInfo.xcprivacy
A bundled file declaring the data the app and its SDKs collect, the tracking domains, and the reasons for using certain APIs
An app that uses required reason APIs without declaring an approved reason, or bundles a commonly used third party SDK that lacks a signed privacy manifest
Add a PrivacyInfo.xcprivacy to the app and confirm every listed third party SDK ships its own signed manifest. Keep the SDK versions current so the signed manifest is present
Required Reason APIs
A defined set of APIs (file timestamps, system boot time, disk space, user defaults, active keyboards) that need a declared approved reason code
Using one of these APIs with no NSPrivacyAccessedAPITypes entry or with a reason code that does not match the use
Declare each required reason API with an approved reason code in the privacy manifest
Tracking domains
NSPrivacyTrackingDomains in the manifest
A domain that performs tracking is contacted but not listed, while ATT consent is not granted
List every tracking domain and gate it behind ATT consent
Export compliance, ITSAppUsesNonExemptEncryption
The encryption declaration every iOS build must answer
Leaving it unanswered parks the build in Missing Compliance, so it never reaches review
Set ITSAppUsesNonExemptEncryption in Info.plist. For a standard app that only uses HTTPS, the exempt answer applies, which removes the per submission prompt
Build with the current SDK
Apple requires new submissions to be built with a recent SDK and Xcode by an annual deadline
An old SDK build after the deadline is rejected at upload
Build with the current required Xcode and SDK before the annual cutoff
The privacy manifest is the single highest impact addition to any pre 2024 checklist. It is the most common modern upload rejection and it scales badly across an enterprise with many vendor SDKs, because each SDK must carry its own signed manifest.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
These are checked when you upload the binary, before a human reviewer ever opens the app. Getting them wrong means the build is rejected or stuck and never reaches review.
The privacy manifest is the single highest impact addition to any pre 2024 checklist. It is the most common modern upload rejection and it scales badly across an enterprise with many vendor SDKs, because each SDK must carry its own signed manifest.
Source section. ADVANCED-2026.md, 1. Apple upload time enforcement (the modern first wall).
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions