Rejection guides / Guideline 2.5.1: Software Requirements (public APIs and frameworks)
Guideline 2.5.1 - Software Requirements: public APIs and framework use
2.5.1 is about how your app uses Apple's frameworks. Either the binary calls something Apple doesn't make public, or it links a framework the app doesn't clearly use or explain.
"Apps may only use public APIs and must run on the currently shipping OS."App Review Guideline 2.5.1, Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
The two usual versions of this rejection
Non-public APIs: Apple's checks found references to private symbols or selectors in your binary. This often comes from a third-party SDK or an old library rather than your own code, and sometimes from a method name of yours that happens to match a private one.
Framework purpose: the guideline also says apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. Apple's examples are HomeKit for home automation and HealthKit for health and fitness with integration into the Health app. If you link HealthKit, HomeKit or a similar framework, the reviewer expects to see that use in the app and in the description.
How to fix it
- Read the message for the exact symbols or frameworks named, then search your code and dependencies for them.
- Update or remove the SDK that references them. Check the SDK's release notes, since many fixed this in later versions.
- If the name clash is your own method, rename it.
- If a framework is linked but not used, remove it and its entitlement. If it is used, say what it does in the app description and point to the feature in review notes.
- Phase out deprecated APIs and build with a current Xcode and SDK.
Common questions
- I never called a private API. Why was I rejected?
- The reference is often inside a third-party SDK, or a method of yours shares a name with a private one. The symbols listed in the message tell you where to look.
- Why does my app description need to mention HealthKit?
- Guideline 2.5.1 says apps should indicate their use of frameworks in the app description. A short line about what the Health integration does is usually what's missing.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- ITMS-91053: Missing API declaration (privacy manifest)
- Guideline 2.1: App Completeness (crashes, bugs, placeholders)
- Guideline 5.1.2(i): Data Use and Sharing (tracking, ATT, third-party AI)
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)