Do we have a time estimate of when this bug will be fixed in Xcode and in which version? Thank you.

I got a reply from App Review about my appeal.

Would that make things faster to just reply on the App Review Board without creating an appeal request? (I also did replied in the Review Board but I also requested an appeal after)

I‘ve just got a reply that’s currently evaluated.

The bug still exists in the latest XCode 26.0 (17A324) and with the latest simulator images iOS 26.0 (23A343)

Thanks for your reply, I've just attached a sysdiagnose file (simctl_diagnose_2025_09_12.08-17-25+0300.tar.gz) collected after I reproduced this behavior to the FB bug.

I've just tested using the new iOS 26 Beta 8 (23A5330a) and call blocking stopped working. After restarting my device following the iOS update, the issue resolved, and call blocking is working as expected on Beta 8. I don't know if it's an edge-case bug though.

I have tested with iOS 26 Beta 7 (23A5326a) and the bug is fixed. Calls are now blocked when a blocking rule is set with addBlockingEntryWithNextSequentialPhoneNumber from CallKit API. I have closed the FB issue. Thanks for fixing that.

Ok, thanks for the clarification. I’ll be waiting for the fix in the next beta (or stable) release version.

I also tested on iOS 26 Beta 6 (Build 23A5318f), but blocked calls still pass through.

The issue persists in iOS 26 Beta 6 (Build 23A5318c). I have attached a new sysdiagnose collected from the latest build for your review in the FB bug.

It is a bug, but including the full international area code (which is what you should already be doing) may get things working even in the beta. I tested this extensively and can confirm that using full international area codes doesn't fix the blocking issue.

Yes, it's a bug in iOS 26 Beta version, check this out: https://developer.apple.com/forums/thread/794740

That's great news! Thank you for the thorough investigation and handling of the issue. I really appreciate the collaborative approach in getting to the root cause. I'll keep an eye on future releases and I'm happy to test this with a (possible) new beta release when the fix is implemented.

Coming at this from the other direction, have you tested this test device that's been reset, doesn't have anything else installed, and has never been called by that number before (well, since the device was reset)? I have also tested with a factory reset device (using the debugging profile) and still the call blocking didn't worked. I have attached a sysdiagnose ZIP as well in the FB bug (sysdiagnose_2025.08.05_10-45-11+0300_iPhone-OS_iPhone_23A5297m.tar.gz)