We tested call blocking on iOS 26 and noticed something strange: the call will not be blocked if an outgoing call was made to its number before. Nevertheless, it will be blocked if we delete the outgoing call record from the Phone.app Recents.
This behavior looks like a bug and is unexpected when using our application. Was this a planned callkit change in iOS 26? Is it possible to get the correct call blocking behavior back?
We set blocking rules with addBlockingEntry(withNextSequentialPhoneNumber:) and this problem is not present in iOS 18 and earlier.
Thank you in advance
This behavior looks like a bug and is unexpected when using our application.
I could argue either side of this issue. There's a "hierarchy" in place that prioritizes different identification/blocking data sources, with the users own contact configuration being considered the most "authoritative". I believe the contact entry would always have overriden an external blocking entry, so the change here is really about giving the outgoing recents call higher "authority".
Was this a planned callkit change in iOS 26?
Yes and no. I'm not sure there was a formal decision that this was a particular case we should handle differently, however, adding support for LiveCaller ID involved large scale changes throughout this area. Part of that process involved reviewing all of our data sources and that review is what changed the behavior here.
Is it possible to get the correct call blocking behavior back?
I don't know. Please file a bug on this and post the number back here.
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
