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

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

@DTS Engineer This issue is still ongoing. We get complaints from users that call blocking isn't working on iOS 26. Are there any updates on this issue? Is a fix planned?

One of the features of our app is the ability to create your own list of blocked calls (spam or unwanted). For example, a user missed a call from an unknown number. He called back and decided it was spam and added this number to his list of blocked calls in our app. But since there's an outgoing call to this number in the Phone.app Recents, it won't be blocked. Removing the outgoing call record from the Phone.app Recents is a rather non-obvious action in this situation. As result, the user blocked the number through our app, but continue received calls from it What's the situation where your app is adding calls to its blocking list which the user has actively called? Blocking will not work if at least one outgoing call has been made to the blocked number. One call back is not an actively called number. But even if a user was actively called with another person, and then decided to interrupt the communication and block him, why should the presence in the Phone.app Recents prevent this? It looks like that the blocking function advertised in the app does not work. I will also add this example to my bug report

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

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

Thanks for the reply We filed bug report with Feedback Assistant: FB20266760 We agree that user contacts have the highest priority. But as for the outgoing recents calls, it is important for us that our application can block them. We will wait for the decision on this issue. If anything else is needed to investigate this issue, please let me know

I tested on iOS 26 Beta 8 (23A5330a) and unfortunately call blocking still doesn't work for me. I set blocking rules with addBlockingEntry(withNextSequentialPhoneNumber:) and it worked fine on iOS 18 and below (I didn't make any changes after updating to iOS 26) I did some tests with different phone numbers. If the phone is not in the call list, it usually gets blocked, but only once. I guess this is because after the first block it still gets into the call list and therefore doesn't get blocked anymore @Papaductions, did you test the scenarios with the phone from recent calls or blocking a call from the same number multiple times in a row? Did it work fine?