A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values ("1" and "2"), and the app immediately launched normally again. I also created a brand-new Xcode 26.4 project and enabled the Enhanced Security capability there. Xcode generated these two entitlements as String values (1 and 2) by default in the new project as well. So at least in my current Xcode 26.4 / OS 26.4 environment, the string-based form appears to be both the Xcode default and the only form that launches normally in testing.

A quick update from my side: After receiving the App Review guidance, I tried changing both of these entitlements from the documented string values to Boolean true: com.apple.security.hardened-process.enhanced-security-version-string com.apple.security.hardened-process.platform-restrictions-string In local testing, that change caused the app to fail to launch on both macOS and iOS. I then changed them back to the documented string values ("1" and "2"), and the app immediately launched normally again. So at least in my current Xcode 26.4 / OS 26.4 environment, the Boolean form appears to break launch, while the string-based form works normally.

For reference, I’m attaching screenshots of: the App Review message that says these entitlements must be boolean and true, and the Xcode 26.4 release note section that says to use the new -string variants with values 1 and 2. These are the two pieces of guidance I’m trying to reconcile.