Yes, this database corruption bug exists unfortunately, similar issue: https://developer.apple.com/forums/thread/806960

The issue persists with iOS 26.2 (23C5033h) Developer Beta. I'm attaching a new sysdiagnose for the issue in FeedbackAssistant. As this CallKit bug/issue is really critical and we constantly have reports from our users, I would appreciate to have a response from an Apple representative for this. Thank you.

As this CallKit bug/issue is really critical and we constantly have reports from our users, I would appreciate to have a response from an Apple representative for this.

I am following up on this thread and my feedback report FB20986470. I have not received any response on either platform. If anyone has information about the status of this CallKit issue, I would appreciate an update.

Thank you for the update. I appreciate knowing this is under active investigation and I hope for a possible fix to be released.

We're also having tons of user complaints about this behavior of when a user has made an outgoing call to a number and he won't be able to block it if he doesn't clean the Recents history log. This behavior mostly looks like a bug but not a normal user case, please provide a fix in this.

We've also filed a bug report for this behavior here (FB21310428) with all use-cases and the necessary details.

I've just got a reply from App Review.