Dear Kevin, thanks for your response, we already filed a report about this (FB15163490). I'd like to share some concerns: Many of our users are confused by this behavior, expecting blocked calls to disappear entirely. Showing blocked calls as unanswered seems to go against the user's intent when blocking a number. Would it be possible to reconsider this design decision? Perhaps offering a user setting to choose whether blocked calls appear as unanswered could be a good compromise.

This is still not fixed in iOS 18.2. We've tested several call blocking apps and this behavior of calls appearing as "unanswered" still exists in all of them. This change is having a significant negative impact on our business: We're receiving numerous negative reviews Users are uninstalling our app Our support team is overwhelmed with complaints This system-level change has severely impacted user trust in call blocking apps and is causing real business damage to developers.

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)

Yes, the issue has been resolved. Thank you for the prompt response.

And unfortunately the only fix that can resolve this is a full device restore.