cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   wmwilson
   Member

   I'm trying to implement multitasking for iOS 4 and I've come across some strange behavior when I quit the app from the new task bar. (By holding down my finger and closing with the red circle) When I quit using this method it ends with a
   GDB: Program received signal: "SIGKILL." after which I can't get the app to load at all.
   I found the following discussion http://www.idevgames.com/forum/showthread.php?p=158369 , but it doesn't totally answer the question of how to fix the error, only how to side step it by not supporting multitasking.
   I used the code at http://www.cocos2d-iphone.org/forum/topic/7326, suggested by zeraien to support multitasking.
   Any one else come across this? Thanks

   Posted 1 year ago #
2. 

   wmwilson
   Member

   UPDATE: I think I only get this when in the debugger, but I get it for any app in the debugger, no just Cocos2D. Probably nothing to worry about, but kind of strange nonetheless.

   Posted 1 year ago #
3. 

   Zammy
   Member

   Have the same problem. Any updates will be nice. I guess ill try it in release, i hope it will not happen.

   Posted 1 year ago #
4. 

   wmwilson
   Member

   I would try the following:
   Run the app from within XCode:
   "Build and Run"

   Then stop it from within in XCode:
   The red stop sign with "Tasks" under it. It should kill the app and debugger.

   Then go back to your iPhone menu and rerun the app. It should startup again.

   Try the multi-tasking and quit the app from the task bar. It should end nicely.

   It worked in my case, it was only when I didn't kill the app from within XCode, and the debugger was still running without me realizing it, that ending from the taskbar caused any trouble. Hope that helps!

   Posted 1 year ago #
5. 

   taber
   Member

   Hi, I just had the same problem, and noticed that Xcode did indeed have the red stop sign lit up waiting to be pushed even though I already killed my app via SIGKILL. Anyway after killing the app through Xcode, relaunching it worked just fine. Thanks for that!

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.