# Has Apple blocked Logic Pro from debugging?

**URL:** <https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562>\
**Category:** macOS\
**Created:** [3 February 2022 18:40 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562 "2022-02-03T18:40:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RexMartin2](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)\
**Post date:** [3 February 2022 18:40 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562/1 "2022-02-03T18:40:37Z")

</div>

I am trying to debug the Logic Pro X issues I posted on this forum on OS Big Sur (Intel) using Xcode 12.5 (the same version I built the plugins with).

I can’t even get started debugging because Xcode refuses to hit any of my breakpoints. Hovering over the breakpoint flag gives the message, “Xcode won’t pause at this breakpoint because it cannot be resolved”.

Cannot be resolved? What does that mean? I have the plugins built in Debug mode as “DWARF with dSYM File” yet I get no tracing at all. I don’t have this issue debugging in other DAWs - what is the problem in Logic Pro? Is there a “trick” or does Apple have it blocked?

---

<div class="post-metadata">

**Author:** ![stw](https://avatars.discourse-cdn.com/v4/letter/s/8e8cbc/32.png) [@stw](https://iplug2.discourse.group/u/stw)\
**Post date:** [3 February 2022 19:15 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562/2 "2022-02-03T19:15:56Z")

</div>

No solution just the Info that Logic debugs fine here. BigSur XCode12.4, Logic10.7.2  
Seems like XCode thinks your code won’t ever be executed…?

---

<div class="post-metadata">

**Author:** ![RexMartin2](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)\
**Post date:** [3 February 2022 19:31 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562/3 "2022-02-03T19:31:53Z")

</div>

> [@stw](#):
>
> Seems like XCode thinks your code won’t ever be executed…

Well then Xcode’s not very smart because I’m sitting here watching it run!

Any idea what is causing that? I built the plugin in Debug mode and - like I posted above - I can debug with no problem in other DAWs, just not Logic.

Xcode 12.5.1, Logic 10.7.2 on Big Sur

---

<div class="post-metadata">

**Author:** ![olilarkin](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/olilarkin/32/2_2.png) [@olilarkin](https://iplug2.discourse.group/u/olilarkin)\
**Post date:** [3 February 2022 21:53 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562/4 "2022-02-03T21:53:07Z")

</div>

In the latest releases of Logic audiounit V2s are hosted in a separate process

[https://developer.apple.com/documentation/audiounit/debugging\_out-of-process\_audio\_units\_on\_apple\_silicon?language=objc](https://developer.apple.com/documentation/audiounit/debugging_out-of-process_audio_units_on_apple_silicon?language=objc)

---

<div class="post-metadata">

**Author:** ![RexMartin2](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RexMartin2](https://iplug2.discourse.group/u/RexMartin2)\
**Post date:** [4 February 2022 01:43 UTC](https://iplug2.discourse.group/t/has-apple-blocked-logic-pro-from-debugging/562/5 "2022-02-04T01:43:09Z")

</div>

Ah - now that you mention it I recall reading something about that. Will take a look at your link. Thank you.