# VST3 build with JUCE 7.0.6 on MacOS is Broken

**URL:** <https://forum.juce.com/t/vst3-build-with-juce-7-0-6-on-macos-is-broken/57304>\
**Category:** MacOSX and iOS\
**Created:** [August 4, 2023, 12:22pm UTC](https://forum.juce.com/t/vst3-build-with-juce-7-0-6-on-macos-is-broken/57304 "2023-08-04T12:22:00Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [August 15, 2023, 2:27pm UTC](https://forum.juce.com/t/vst3-build-with-juce-7-0-6-on-macos-is-broken/57304/20 "2023-08-15T14:27:47Z")

</div>

> [@dhilowitz](#):
>
> `OTHER_CODE_SIGN_FLAGS=--timestamp --options runtime`

My guess is that the problem originates here - I think these flags will apply to all targets (not just the plugin), so the manifest generator will be built with the hardened runtime. This fails because apps using the hardened runtime can’t load adhoc-signed bundles, and the bundle isn’t release-signed until after the manifest is generated.

I recommend instead just setting `OTHER_CODE_SIGN_FLAGS=--timestamp`, and setting “Use Hardened Runtime” to “Enabled” in the Xcode (macOS) exporter in the Projucer. The Projucer knows that when the option is set here, it should only apply to the final plugin binary, rather than to every target in the project.

---

_[View the full topic](https://forum.juce.com/t/vst3-build-with-juce-7-0-6-on-macos-is-broken/57304)._