App Store 2.5.4 rejection: Background modes

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps declaring or using background services without the matching user-facing functionality.

A background mode may have been added to keep the app alive, but Apple expects it to serve its documented purpose. Guideline 2.5.4 covers services such as audio, location, and internet calling when the app isn’t in the foreground.

Compare declarations with real features

Ask your developer to inspect the build’s background modes and the libraries that use them. Does the app really play audio, navigate, or handle calls in the way that mode supports? We’d test what happens after the user leaves the app, not just the initial screen.

Remove unnecessary modes

Remove a mode that doesn’t support a legitimate feature and use the appropriate supported scheduling mechanism for the task. If the mode is necessary, make the feature reviewable and explain why its background behavior is part of the user’s task.

Test starting, stopping, and leaving the feature. Check that background activity ends when it should. Provide Apple the exact route to the feature, the declared mode it needs, and the corrected build if configuration changed.

Messages this guide can help with

App Store 2.5.4 rejection; app store 2.5.4 denial; Guideline 2.5.4; Background modes

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review