Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As soon as I launch app in simulator, Xcode switches to main.m and I see this error momentarily most of the time but the weird part is, this is momentarily, error disappears and then app launches.
for me it seems like Xcode gets confused for a while and then it realizes oh there’s no error and continues… strange…
I’m more concerned that if there’s something I should catch it now but I’m unable to.
This happens when you launch an app and still have it launched from before. Sigkill message is from the already running session – it received a sigkill so a new session can be started. Nothing to worry about.
You can see this kill and quit signals if you have debug console turned on.
If you don’t want too see this error you should stop the running session (stop button: stop the running scheme or application) prior to running a new one.