App Store 2.5 rejection: Software requirements
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps with rejected API use, background behavior, browser engines, or integrations with device features.
The app works on your phone, but Apple has flagged how it uses the system. Guideline 2.5 covers technical requirements that can come from your code or a library bundled with it. The subrule is the useful starting point.
Give your developer a specific investigation
Keep the cited number, build, and reviewer evidence. Ask which framework, entitlement, or dependency implements the feature. We’d check the shipped binary and its configuration, since source settings don’t always show what a build tool included.
Use the rules below to narrow the issue: public APIs, downloaded code, background services, network support, and device integrations each have different checks.
Test the corrected integration
Remove or replace the unsupported behavior and rebuild when the binary or its permissions changed. Verify the feature on supported devices, including denied permissions and background transitions where relevant.
Explain the technical correction in ordinary terms in your reply, then provide the steps Apple needs to test it. A setting removed from configuration is only a fix once the submitted build reflects that change.
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 Checked 22 September 2026