I am having the same issue, can’t hit any breakpoint in ported plugins.
I see that one week ago they submitted a bug regarding it in:
https://developer.apple.com/forums/thread/674706
Lets hope they will fix it soon.
1 Like
Update from Apple regarding disabling SIP to to debug Logic:
“Unfortunately, disabling SIP in order to being able to debug AUHostingServiceXPC_arrow is the only solution right now. We are investigating alternatives to make this possible in the future.”
3 Likes
Has the situation improved in someway with the latest Logic Update?
No
I don’t even see this AUHostingServiceXPC_arrow listed in the processes … How that?
have you loaded the plugin, or another plugin that uses it? it’s not loaded until needed…
I have loaded the plugin after I attach, does the service appear once at least 1 plugin is loaded?
yes, a plugin has to be loaded in order for the service to appear.
1 Like
Thanks a lot ! Looks like they changed something related to channels in the last Logic 10.6.2 version …
AUHostingServiceXPC is the Intel process (e.g. Rosetta AUs), while AUHostingServiceXPC_arrow is the Apple Silicon process. Please to not expect these names to be “forever names”.
2 Likes
This solves some issues, but for me when I introduce Logic as part of my ‘scheme’ in xcode it keeps opening WITHOUT Rosetta. When I open from the app it opens WITH Rosetta.
Following up on this…
Is it possible to attach Xcode’s debugger to Live / Logic etc on Apple Silicon machines without disabling SIP?
And if so how?
For Live you can resign the app - there’s info on the site if you search for it
Not sure about Logic, can’t remember what the state of that is as it’s been a while since I’ve had to debug it, but yes, think you have to disable SIP still.
Pretty sure i’ve never disabled SIP, has something changed recently? Maybe I’ve done all my debugging in standalone for a year and not noticed 
For Logic, you need to disable SIP.
The article still seems to be valid. SIP blocks spying on other system processes, which is an important security feature. Having it, adds a level of protections for all users, but debugging (even your own code) relies on breaking exactly that. So, having a few development machines less secure – by disabling SIP – seems like a reasonable compromise. But it is annoying. Maybe Apple could add an additional entitlement to allow debugging specifically of the AUHostingServiceXPC/AUHostingServiceXPC_arrow process without disabling SIP in general. Please all file feedback for Apple on this!
This security layer does not exist on Intel based machines, so you will not have SIP protection.
Anyone found a workaround for this? I have some customers facing the same issue, but I’m not able to replicate it all the times.
unfortunately this is a generic popup displayed when a plugin can’t be loaded - 99 times out of a hundred it’s a bug in the code. i tend to try and debug AUs in Live as it’s easier to debug than logic on silicon
This is happening with plugins already loaded in existing sessions and it’s basically happening with all of our line of plugins (more than 30) and since the later logic pro 10.7.x versions
Have you tried with the latest version of JUCE?
1 Like