How can I attach the debugger to a Service Extension?

Typically, I would have the scheme configured to "Wait for executable to be launched", though I don't see a way to attach the debugger in that way.


Actually, I'm not sure I can figure out how to attach the debugger to any Notification extensions (content or service).


Has someone been able to do this? Debugging without being able to use breakpoints is painful.

How is it possible that no one has an asnwer to this?


`print` and `NSLog` aren't even showing up in the device log, this is impossible.

I found a workaround.


If you send a push, the extension will spin up, and you can connect to it through the Debug > Attach to Process menu.

Unfortunately, the framework I'm using isn't debugging correctly, I get plenty of this, which is astonishing and useless:


Printing description of url:
url = <could not resolve type>

I learned that, using the name of the extension class, I can pointedly target the extension by using Debug > Attach to Process by PID or Name...


I'm still having trouble getting the symbols to resolve or getting the variables to print in the debugger. Was anyone else able to figure this out?

How can I attach the debugger to a Service Extension?
 
 
Q