I recommend that you escalate this via the support channel for the third-party tools you’re using.
For context, post-notarisation errors usually fall into one of three categories:
-
The app doesn’t pass Gatekeeper.
-
The app crashes at launch with a code signing error.
-
The app crashes once it’s started executing its own code.
I strongly suspect that this problem falls into the last category. The standard process for debugging that involves looking at where the code crashed and working back to find which specific hardened runtime security enhancement triggered that misbehaviour. You can then either fix the code or apply a specific exception entitlement.
If this were your code I’d be happy to help you work through these steps. However, it’s not your code and thus you can’t run the tests I need you to run. Hence the advice that I started this response with. I suspect that the Qt folks have already worked through this process many times and will be able to advise you on how best to deal with it.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
