Guideline 2.5.1 rejection: Non-public or deprecated APIs, frameworks used off-purpose
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.5.1 - Performance - Software Requirements
What Apple's guideline says
Apps may only use public APIs and must run on the currently shipping OS.
From App Review Guidelines, 2.5.1, as revised October 16, 2026.
Common causes
- A private or non-public API called by your code or by a third-party SDK
- Deprecated features or frameworks that will not be supported in future OS versions
- A framework such as HealthKit or HomeKit used for something other than its purpose
- A framework integration not mentioned in the app description
How to fix it
- Find the symbol or framework named in the message, in your code and in every SDK
- Replace non-public APIs with public ones, or update the SDK that uses them
- Replace deprecated technology
- Use HealthKit, HomeKit, and similar frameworks only for their intended purpose, and say so in the description
- Ship a new build and reply with what you replaced
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 2.5.1, build [number] no longer uses [API or framework]. It came from [our code / SDK name], which we [replaced / updated to version x]. Thank you.
Real cases: others who got 2.5.1
No public cases logged yet.
Questions developers ask about 2.5.1
What does a Guideline 2.5.1 rejection mean?
Your app uses non-public APIs, relies on deprecated technology, or uses a framework like HealthKit or HomeKit for something other than its intended purpose.
Why do apps get rejected under Guideline 2.5.1?
Common causes, based on Apple's guideline text: A private or non-public API called by your code or by a third-party SDK; deprecated features or frameworks that will not be supported in future OS versions; A framework such as HealthKit or HomeKit used for something other than its purpose; A framework integration not mentioned in the app description.
How do I fix a Guideline 2.5.1 rejection?
1. Find the symbol or framework named in the message, in your code and in every SDK. 2. Replace non-public APIs with public ones, or update the SDK that uses them. 3. Replace deprecated technology. 4. Use HealthKit, HomeKit, and similar frameworks only for their intended purpose, and say so in the description. 5. Ship a new build and reply with what you replaced.
Do I need a new build for Guideline 2.5.1?
Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 2.5.1?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.5.1, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.
Stuck on 2.5.1?
Do it yourself, faster
App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.
Get the kit, $12Have it written for you
Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.
AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.
Reply service, $29Related rejections
See also: 2.5.2 executing code · 2.5.4 background modes · ITMS-91061 and 91053 privacy manifest emails
Source: Apple's App Review Guidelines, section 2.5.1, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.