# Can't debug AUv3 in a host on iOS

**URL:** <https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732>\
**Category:** MacOSX and iOS\
**Created:** [December 2, 2025, 9:32am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732 "2025-12-02T09:32:21Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![phraemer](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/phraemer/32/10076_2.png) [@phraemer](https://forum.juce.com/u/phraemer)\
**Post date:** [December 2, 2025, 9:32am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/1 "2025-12-02T09:32:21Z")

</div>

I can of course debug the Standalone app but debugging the AUv3 in a host used to work. I would choose the scheme MyPlugin\_AUv3, edit the executable to “Ask on Launch” and I could choose AUM for example. Then start debugging, which would launch AUM, I’d insert the plugin and I could debug and would get logging.

Now Xcode tells me

> “Direct installation of an App Extension is not supported.  
> Domain: com.apple.dt.CoreDeviceError  
> Code: 3002  
> Recovery Suggestion: To debug MyPlugin.appex use the App Extension scheme and set the exectable in the Run scheme action to ‘Ask on Launch’ or an application built by this project that will trigger the App Extension.”

But if I debug the Standalone scheme and choose “Ask on Launch” and then choose AUM, AUM will launch but when I insert the plugin Xcode does not attach. I.e. no breakpoints, no logging.

Anyone have it working?

macOS 26.1  
Xcode 26.1

iOS 26.1

HEAD of JUCE develop branch

---

<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:** [December 2, 2025, 11:06am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/2 "2025-12-02T11:06:42Z")

</div>

Have you tried launching the host + plugin, and then attaching to the plugin process once it’s already running?

---

<div class="post-metadata">

**Author:** ![phraemer](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/phraemer/32/10076_2.png) [@phraemer](https://forum.juce.com/u/phraemer)\
**Post date:** [December 2, 2025, 11:16am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/3 "2025-12-02T11:16:02Z")

</div>

Interestingly I can do that and breakpoints work but still no logging.

Will need to be able to debug startup of the plugin too though so this is better, thank you, but not yet ideal.

---

<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:** [December 2, 2025, 11:18am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/4 "2025-12-02T11:18:53Z")

</div>

In the worst case you could temporarily add a sleep or a loop while `Process::isRunningUnderDebugger()` returns false, just after startup. It’s not perfect, but that should allow you to debug the majority of the startup sequence.

---

<div class="post-metadata">

**Author:** ![phraemer](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/phraemer/32/10076_2.png) [@phraemer](https://forum.juce.com/u/phraemer)\
**Post date:** [December 2, 2025, 11:32am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/5 "2025-12-02T11:32:23Z")

</div>

I also made this little hack in juce\_SystemStats\_mac.mm and got back logging:

```auto

void Logger::outputDebugString (const String& text)
{
   #if JUCE_IOS
    NSLog (@"%s", text.toRawUTF8());
   #else
    // Would prefer to use std::cerr here, but avoiding it for
    // the moment, due to clang JIT linkage problems.
    fputs (text.toRawUTF8(), stderr);
    fputs ("\n", stderr);
    fflush (stderr);
   #endif
}

```

---

<div class="post-metadata">

**Author:** ![aqeelaadam](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@aqeelaadam](https://forum.juce.com/u/aqeelaadam)\
**Post date:** [January 23, 2026, 8:05pm UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/6 "2026-01-23T20:05:24Z")

</div>

I’m having this problem as well on Xcode 26.2 and iOS 18.5, FWIW.

@phraemer could you please explain the process of launching the host and then attaching to the plugin process? I can’t seem to get anything going, no matter what I try in the AUv3 scheme. Any combination of executable and launch options seems to just instantly give me the error in your OP.

---

<div class="post-metadata">

**Author:** ![aqeelaadam](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@aqeelaadam](https://forum.juce.com/u/aqeelaadam)\
**Post date:** [January 26, 2026, 6:05pm UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/7 "2026-01-26T18:05:24Z")

</div>

For anyone else with this issue: it seems like Xcode 26 is the main issue. Using 16 instead fixed the issue for me.

---

<div class="post-metadata">

**Author:** ![phraemer](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/phraemer/32/10076_2.png) [@phraemer](https://forum.juce.com/u/phraemer)\
**Post date:** [January 27, 2026, 8:55am UTC](https://forum.juce.com/t/cant-debug-auv3-in-a-host-on-ios/67732/8 "2026-01-27T08:55:01Z")

</div>

I have to start the plugin in a host, then in Xcode use Debug \> Attach To Process \> select the plugin process

Can’t seem to select a host to launch and then just add the plugin anymore, which would be necessary for debugging initialisation of the plugin in a host without resorting to tricks like adding a delay somewhere 😕
