This is the same issue I'm seeing on a SwiftUI App-Kit based app as well.
The test target was already disabling Enable Hardened Runtime though, but the app target had it enabled. And of course, Xcode issues warnings if you have it disabled for the app target.
Is this correct that we effectively have to build with Hardened Runtime disabled for the app to work around this bug and live with the Xcode project warning for now?