The issue persists in iOS 26 Beta 6 (Build 23A5318c). As come quick follow up on this, yes, the issue is not fixed in beta 6. As some background context, there is a significant testing process before every beta is released, so it's not unusual for a bug to be completely fixed (meaning, all code changes have been submitted and are in that release) but miss the next beta release because that release is already locked and in testing. I also tested on iOS 26 Beta 6 (Build 23A5318f), but blocked calls still pass through. In a similar vein, the minor letter (c vs f) is primarily used to designate differences that are outside the actual code/build, like the distribution mechanism (in this case, the developer seed vs. the public beta). While it's possible there have been exceptions, I would not expect there to be ANY substantial behavioral difference* between those two build. *The obvious exception would be issues caused by differences in the install or configuration pipeline, which is why