Re: Puzzle with Hardened Runtime entitlement

Jack Brindle

Hardened Runtime is not currently a requirement for Notarization, but it appears that you have to submit the app using the command-line tool for notarization to happen properly. All my attempts at submitting using the Xcode archive method forces me to enable hardened runtime. I have not attempted at submission using Xcode 11, but when submitting with Xcode 10, I have had no problems with hardened runtime so far.

By the way, it appears that hardened runtime causes issues within Apple’s frameworks related to input monitoring. With it, we were not able to get the input monitoring prompt to appear. Removing it allowed our apps to operate properly. These apps do extensive work with BLE keyboard control.

So, you might want to use the command line method for submission to get around this, at least until the requirements change in January.


On Oct 31, 2019, at 6:25 PM, Graham Cox <graham@...> wrote:

I have an app I’d like to notarize for distribution outside the app store.

To do this, it requires the hardened runtime entitlement.

I have added that in the project settings.

When I try and submit the app for notarization, it says “hardened runtime not enabled”.

But it is:

<Screen Shot 2019-11-01 at 12.21.49 pm.png>

I have no idea what’s going on, or how to fix this. I’m using Xcode 11.0

One thing that does seem odd, there is no “<app>.entitlements” file in the project. Changing settings in the Xcode UI doesn’t add such a file. Is this the problem?


Join { to automatically receive all group messages.