Home/ Questions/Q 8197741
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T05:48:11+00:00

I have Weird problem,When i close my app via task manager , my app

  • 0

I have Weird problem,When i close my app via task manager , my app gets crashed on the line

int retVal = UIApplicationMain(argc, argv, nil, @"AppDelegate");

throwing “Thread : 1 signal SIGKILL” error,and i can’t reopen my app at all. other times it works pretty well.
Please some one help me with this problem.
I am new to cocos-2d so please be gentle 🙁 , thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As far as I know, this is normal, expected behavior. The reason it seems weird, I think, is that when you run from Xcode, your executable is attached to the debugger in Xcode, so it sometimes prevents things from executing (for example, in a crash or SIG_KILL scenario). This is just giving you a hint as to what apple is doing when you use the task-bar to close the app… it sends SIGKILL to the process 🙂

    EDIT: for the curious, I tested a little and found that applicationWillTerminate: is not called first, which is actually encouraging as a consumer of apps. You really are SIGKILLing these things. I think this means (with the background-processing workflow) that the only case when that method will be called is if you opt out of background execution. The good news is that in order to kill an app this way, you need to move it to the background first, so the canonical place for teardown is applicationWillResignActive: but you knew that…

    EDIT: instructions for avoiding the can’t-run-again issue:

    1. Build and Run the app on your device from Xcode
    2. As soon as the app is “up and running”, click “stop” in Xcode
    3. When the app has closed, it is now “detached” from Xcode and you can terminate it and re-open as often as you wish. Just keep in mind that it will no longer log to Xcode any NSLog calls or otherwise.
    • 0