# Xcode 11 not launching executable

**URL:** <https://forum.juce.com/t/xcode-11-not-launching-executable/35605>\
**Category:** General JUCE discussion\
**Created:** [October 9, 2019, 4:41am UTC](https://forum.juce.com/t/xcode-11-not-launching-executable/35605 "2019-10-09T04:41:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ttg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ttg/32/14456_2.png) [@ttg](https://forum.juce.com/u/ttg)\
**Post date:** [October 9, 2019, 8:29am UTC](https://forum.juce.com/t/xcode-11-not-launching-executable/35605/2 "2019-10-09T08:29:53Z")

</div>

See this -

> [@Apple Gatekeeper notarised distributables](https://forum.juce.com/t/apple-gatekeeper-notarised-distributables/29952):
>
> Hi Apple looks to be furthering gatekeeper protection with additional checks on distributed binaries, we can see some details about it here: [https://developer.apple.com/developer-id/](https://developer.apple.com/developer-id/) and a little more from Ars here: [https://arstechnica.com/features/2018/09/macos-10-14-mojave-the-ars-technica-review/10/#h3](https://arstechnica.com/features/2018/09/macos-10-14-mojave-the-ars-technica-review/10/#h3) It seems Apple wants to perform some kind of basic review of signed binaries and to then act as a notary on the developer’s signature, vouching for it not containing malware etc, so they can …

With newer hardened hosts you need to disable sip or re-sign them with appropriate entitlements.

---

_[View the full topic](https://forum.juce.com/t/xcode-11-not-launching-executable/35605)._
