App Store 2.5.2 rejection: Downloaded code and app containers
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps downloading executable functionality or accessing files outside their permitted app storage.
Downloading content and downloading a new feature aren’t the same review question. Apple’s 2.5.2 requires apps to stay within their designated storage area and restricts downloading or executing code that introduces or changes functionality.
Inspect what the download contains
Ask your developer to classify downloaded files: data, media, scripts, or executable code. Check update systems, plugins, and third-party components. We’d compare what Apple reviews with what users receive after launch.
Apple provides a limited exception for educational coding apps, with conditions including making the supplied source viewable and editable. Apps offering mini apps or other hosted software should also examine 4.7 rather than assuming all downloaded software has the same treatment.
Use a permitted delivery method
Remove the prohibited download or move the functionality into the reviewed build. Correct file access to use supported container and document APIs. If relying on an exception, explain exactly how its conditions are met.
Test a fresh installation and its first update/download cycle. Provide Apple the download’s purpose, contents, and corrected behavior without disguising executable changes as “content.”
Messages this guide can help with
App Store 2.5.2 rejection; app store 2.5.2 denial; Guideline 2.5.2; Downloaded code and app containers
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.5.2 Checked 22 September 2026