App Store 2.5.12 rejection: Call and message spam blocking

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps using CallKit or SMS fraud extensions to identify or block calls and messages.

Apple wants to know why a number is blocked and what happens to the information your app sees. Guideline 2.5.12 limits blocking to confirmed spam and requires clear disclosure of the feature and list criteria.

Inspect the list and the data flow

Check how numbers enter the blocking list, how an incorrect entry is handled, and whether the store description explains the criteria. We’d inspect the provider behind an imported list instead of assuming its “spam” label establishes accuracy.

Trace data accessed through the extension. Apple restricts its use to operating or improving the app or extension; using it for tracking or unrelated profiling doesn’t fit that purpose.

Correct and demonstrate

Remove unsupported entries or inappropriate data uses and update the description. Test with controlled numbers and messages without contacting unrelated people. Verify that the app’s behavior matches its published explanation.

Give Apple the criteria, relevant data handling, and safe steps to test the feature. If a third-party feed caused the problem, explain what changed in that feed or your handling of it.

Messages this guide can help with

App Store 2.5.12 rejection; app store 2.5.12 denial; Guideline 2.5.12; Call and message spam blocking

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