I\'m building a set of Notification Extensions (Service/Content). I\'m unable to connect to Xcode debugger or even log out to the device log or console.
Is there any
If you have tried all the above solutions and still scratching your head and wondering why break point point is not being called. Then try checking the deployment target
of your extension
it should be less or equal to your device OS.
For me, the deployment target was higher than the device OS.
In my case (Xcode 11.1) debug starts after this steps:
Not sure if this will be helpful, but we have multiple builds of the same app (alpha, beta, etc). Kept getting a "don't have permissions to attach" error when trying to debug. Opening up the processes list, I noticed that there were 2 processes named notification-extension
so xcode must have been defaulting to the one of the other build. By manually selecting the right one, or deleting the other builds from my phone things started working again.
Change the target to run the extension
then select run and choose your app from the 'Choose an app to run:' window.
This worked for me to stop at breakpoints in the extension and see the extension log:
Choose an app to run
Message from debugger: Terminated due to signal 9
after step 6.
[Update: Terminating the app manually on the device doesn't seem to be necessary, try either way if it doesn't work.]Debug > Attach to Process by PID or Name
I have tried as per brendan's Answer but is not working for me at all!
I am getting below error in console
Program ended with exit code: 0
Then after searching on google i have checked this answer. however this also not worked for me for while!
Then i have tried same steps again as given in answer, After stopping my current running app. then follow same steps.For clarity i am writing this steps as below:
After running the app that contains the extension,
1) Set your breakpoint in the extension
2) Select Debug / Attach to Process by PID or name
3) Enter the name of the extension target
4) Trigger the push notification
Before step 2 make sure to stop your current running app.