App Store 2.5.1 rejection: Public APIs and intended framework use
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps using private, deprecated, or incorrectly applied platform APIs and frameworks.
You may not have added the rejected API yourself. Under 2.5.1, the app and its dependencies need to use public APIs, support the current operating system, and use frameworks for their intended purpose.
Find the code that makes the call
Give the developer the API or framework Apple identified. Inspect third-party libraries and the compiled build as well as your own source. We’d confirm which dependency version ships before assuming an upgrade has removed the problem.
Check that the integration’s purpose matches the framework. For example, access to a health framework needs a health-related use, not an unrelated data-collection feature.
Replace and retest
Use the supported public API or update/remove the responsible dependency. Phase out deprecated integrations and accurately describe the remaining functionality in the app’s listing.
Build again and exercise the feature on the currently shipping OS. Report the library or API changed and how the reviewer can reach the feature. Keep the explanation specific; “updated dependencies” doesn’t establish that the flagged call is gone.
Messages this guide can help with
App Store 2.5.1 rejection; app store 2.5.1 denial; Guideline 2.5.1; Public APIs and intended framework use
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.1 Checked 22 September 2026