(Xcode 26.2, iPhone 17 Pro) I can't seem to get hardware tag checks to work in an app launched without the special Hardware Memory Tagging diagnostics. In other words, I have been unable to reproduce the crash example at 6:40 in Apple's video Secure your app with Memory Integrity Enforcement. When I write a heap overflow or a UAF, it is picked up perfectly provided I enable the Hardware Memory Tagging feature under Scheme Diagnostics. If I instead add the Enhanced Security capability with the memory-tagging related entitlements: I'm seeing distinct memory tags being assigned in pointers returned by malloc (without the capability, this is not the case) Tag mismatches are not being caught or enforced, regardless of soft mode The behaviour is the same whether I launch from Xcode without Hardware Memory Tagging, or if I launch the app by tapping it on launchpad. In case it was related to debug builds, I also tried creating an ad hoc IPA and it didn't make any difference. I realise there's a wrinkle here