iOS 26 23A341 - CallDirectory does not block calls anymore

Question

mrn4 OP

Created Sep ’25

Replies 5

Boosts 1

Participants 4

Hi,

Since I updated my phone to 23A341, my Call filtering app is not blocking calls anymore.

Same release checked on iOS 18 phone, it is working.

I still see the callkit logs into the Console showing that numbers are loaded into the iOS-managed SQlite DB but the calls are not blocked nor identified.

Anyone with the same issue?

BR

Answered by DTS Engineer in 858904022

I still see the callkit logs into the Console showing that numbers are loaded into the iOS-managed SQlite DB but the calls are not blocked nor identified.

As the post above referenced, we're not currently blocking calls that are recent outgoing call targets. Can you confirm whether or not that applies in your case?

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

Boost

Answer 1

mrn4 OP

Sep ’25

FB20272976

0

Answer 2

Reidak18 OP

Sep ’25

Please check this out: https://developer.apple.com/forums/thread/800415

I guess it can be the same case

The call will not be blocked if an outgoing call was made to its number before. It will be blocked if we delete the outgoing call record from the Phone.app Recents

Can you test this scenario on your device please? I believe that if multiple people have this problem, Apple will prioritize fixing it

Thank you in advance

0

Answer 3

DTS Engineer OP

Apple

Sep ’25

Accepted Answer

I still see the callkit logs into the Console showing that numbers are loaded into the iOS-managed SQlite DB but the calls are not blocked nor identified.

As the post above referenced, we're not currently blocking calls that are recent outgoing call targets. Can you confirm whether or not that applies in your case?

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0

Answer 4

mrn4 OP

Sep ’25

Indeed I used test numbers that I called previously. Can you update the doc? I did not see this information anywhere.

Thank you

0

Answer 5

DTS Engineer OP

Apple

Sep ’25

Indeed, I used test numbers that I called previously. Can you update the doc?

Please file a bug asking the documentation to be updated and post the bug number back here.

Having said that:

I did not see this information anywhere.

...while the behavior above is new in iOS 26, there have ALWAYS been exceptions that would cause us to bypass a call directory entry. Notably, the user direct contact takes precedence over CXCallDirectory. This has always been the case but has never been formally documented as such.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0