In addition, when using the addIdentificationEntryWithNextSequentialPhoneNumber to identify calls, identification works great. But not when using addBlockingEntryWithNextSequentialPhoneNumber. I've tried lots of call blocking apps (6 apps) and none of them was able to block a call anymore, so this indicates that this should be an issue in iOS side.

Thanks for the reply. We're using CXCallDirectoryProvider and we've made no changes in our end. The strange part is that all the call blocking apps I've tried didn't blocked any calls based on my given rules (but when testing with iOS 18.x they did). After checking the logs, I didn't found anything suspicious. Did you made any changes to CXCallDirectoryProvider or CallKit that may prevent call blocking? (or maybe with the new changes that introduced with call filtering etc in iOS 26)

Thanks for the update, we hope that this will be resolved.

Thank you for sharing your test results. However, I'm observing a different behavior on iOS 18.2 (22C152): When a call is blocked via CallKit, it appears as "unanswered" in the call history The notification badge appears in the Phone app when testing in iOS 18.2 There's no indication of which app blocked the call in the Recents Tab log My testing scenario: Fresh install of a CallKit app with call blocking functionality Set up app rules to block a specific number Call from that number (not blocked at OS level or anywhere else) to my iPhone Call comes through as "unanswered" in history

Bumping this post, as the bug is still not fixed in iOS 18.2 as promised. Blocked calls still appear as "unanswered" in the Recents Tab in the Phone app. This behavior change is having a significant negative impact on our business: We're receiving numerous negative App Store reviews Users are uninstalling our app thinking it's not working Our support team is overwhelmed with complaints about this issue This system-level change has severely impacted user trust in call blocking apps and is causing real business damage to developers. Any timeline on when this counterintuitive behavior will be addressed? Our users and business continue to suffer from this change.

Thank you for your response. However, I have some important points to raise: Could you please point to the forum posts where developers confirmed this was resolved? I've tested several other call blocking apps on iOS 18.2, and they all exhibit the same behavior - blocked calls appearing as "unanswered". This suggests the issue is not resolved. Most critically, this iOS 18 behavior change is having a significant negative impact on our business: We're receiving numerous negative App Store reviews Users are uninstalling our app thinking it's not working Our support team is overwhelmed with complaints about this issue This system-level change has severely impacted user trust in call blocking apps and is causing real business damage to developers.

@DTS Engineer Following up, have you had a chance to review the feedback report (FB16093992)? The behavior with blocked calls appearing as "unanswered" is still present in iOS 18.2. Any insights would be appreciated.

@DTS Engineer Following up, have you had a chance to review the feedback report (FB16093992)? The behavior with blocked calls appearing as "unanswered" is still present in iOS 18.2. Any insights would be appreciated.

We have filed a bug report with bug number: FB16093992

The issue persists with new incoming blocked calls in iOS 18.2. We understand that existing calls from before the update would retain their previous status, but even fresh blocked calls are still appearing as unanswered (in the Recents Tab) rather than being labeled as "Blocked". To be specific: when a new call is blocked by our Call Directory extension in iOS 18.2, it: Successfully blocks the call (doesn't ring) Shows up in the call history as unanswered Has no indication that it was blocked We've filed a new bug report here: FB16093992

@DTS Engineer Thank you for the update about iOS 18.2, but we're observing that blocked calls still appear as "unanswered" in the call history in iOS 18.2, contrary to what was indicated would be fixed in beta 3 (22C5131e). To clarify: blocked calls still don't ring, but continue to show up as "unanswered" in the call history instead of being marked as "Blocked" as was suggested. Is there any additional information about when this behavior might be addressed? Our users continue to find this confusing as they expect blocked calls to either be labeled clearly or not appear in their history at all.

Thank you for the update. This change in iOS 18.2 beta 3 sounds much better - having blocked calls labeled as "Blocked" and showing which app blocked them makes much more sense for users. This should significantly reduce any confusion. Really appreciate your help in addressing this issue.

Thank you for explaining the contacts behavior. While we understand the rationale behind not blocking contacts, we're currently dealing with a more pressing issue in iOS 18 that's causing significant user confusion: Blocked calls (non-contacts) now appear as "unanswered" in the call history, whereas before iOS 18, they wouldn't appear at all. Our users are finding this new behavior confusing and counterintuitive, as they expect blocked calls to be completely hidden. To be clear - while the blocking itself works (phone doesn't ring), the calls still show up as "unanswered" in the history. We're receiving numerous complaints about this change, as users think their call blocking isn't working when they see these "unanswered" calls. We've already submitted feedback (FB15746906) about this, but I wanted to highlight how this is impacting the user experience. Would it be possible to reconsider this behavior in a future iOS update?

@echu No, the blocking isn't working when a phone number exists in the user's contact list.

Dear Elliot, I wanted to provide a brief update and reiterate our concerns: User Feedback: Since our last exchange, we've received more user complaints about this behavior. Many find it confusing and counterintuitive. Privacy Concerns: Some users have expressed privacy worries, as blocked numbers are still visible in their call history. App Store Reviews: We're seeing negative reviews mentioning this issue, which affects our app's reputation despite being an iOS behavior. Purpose of Call Blocking: This feature appears to contradict the fundamental purpose of call blocking. When users block a number, they typically expect to eliminate all traces of communication from that source, including entries in their call history. We understand that changes can't happen overnight, but we hope this feedback helps illustrate the impact on users and developers. Is there any update you can provide on whether this behavior might be reconsidered in future iOS versions? Thank you again for your time and consideration.