Unknown Crashes happened in SpriteKit

Question

I am new in spriteKit and am developing a game. I had some memory problem, which I solved, but after playing the game several times it now crashes due to 'bad access'.

At the end of each level I present an Image to indicate whether the user wins or loses, and remove all SKSpriteNodes in the SkScene:

[node removeFromParent];

and I do not use Preloading for textureAtlas.

This link is from my Xcode:

my Error Image 1

My Error Image 2

Crash Log:

Crash Log Description

i found the Error using test flight

3 UIKit 0x30ee700c _UIGestureRecognizerSendActions 4 UIKit 0x30d92502 -[UIGestureRecognizer _updateGestureWithEvent:buttonEvent:] 5 UIKit 0x31139af4 ___UIGestureRecognizerUpdate_block_invoke

possibly related to this: http://stackoverflow.com/questions/22399278/sprite-kit-ios-7-1-crash-on-removefromparent — CodeSmile, Apr 21 '14 at 23:02
@LearnCocos2D may be but can you tell me how to solve it ? i do not know anything about SKNodeShape and i do not use it — khaled, Apr 21 '14 at 23:59
Try adding an exception breakpoint to pinpoint which line causes this error — ZeMoon, Apr 22 '14 at 09:14
Also, a call stack should be logged when this error occurs. Please post that as well. — ZeMoon, Apr 22 '14 at 09:15
@akashg i already post the stack when error occurs in the two images in the question my Error Image 1 My Error Image 2 — khaled, Apr 22 '14 at 09:43
The stack needs to be symbolicated. The images you have posted cannot be understood — ZeMoon, Apr 22 '14 at 09:44
Let the game crash completely, and then the symbolicated stack should be logged in the debugger. — ZeMoon, Apr 22 '14 at 09:46
@akashg i am sorry but can i make it in the development mode after the app is completely crashed how can i get the symbolicated stack in development mode ? — khaled, Apr 22 '14 at 09:58
@akashg it happened in Device only how can i get the symbolicated stack log — khaled, Apr 22 '14 at 10:20
http://stackoverflow.com/questions/7375851/iphone-how-to-symbolicate-translate-read-device-crashlog-with-xcode-4 — ZeMoon, Apr 22 '14 at 10:42
This does not look like the crash log for your app. Have you tried setting an exception breakpoint? — ZeMoon, Apr 22 '14 at 11:18
@akashg i made archive and put it on my ipad then get what is written in console is this right ? — khaled, Apr 22 '14 at 11:21
This is the correct crash log, but like I said, this needs to be symbolicated. — ZeMoon, Apr 22 '14 at 12:22
@akashg yes i am yes gesture Recogniser in Skcenes but it 's crash in other sKcene — khaled, Apr 24 '14 at 14:06

score 1 · Accepted Answer · answered Apr 22 '14 at 12:08

1

I cannot understand your crash log, you can debug this while running your app itself at runtime.

A simple way to prevent EXC_BAD_ACCESS can be:

if (node != nil)
{
    [node removeFromParent];
}

answered Apr 22 '14 at 12:08

ZeMoon

20,054
5
57
98

1

i think send Message to nil object does not crash the app – khaled Apr 22 '14 at 12:23
You still have not been able to point out where exactly you get this crash – ZeMoon Apr 22 '14 at 13:28
can you check Crash log description Link in the Question – khaled Apr 22 '14 at 13:53
"I think" is not valid, unless you have actually tried it out. The Crash Log link is not Symbolicated. Check this: http://kevincupp.com/2011/05/12/symbolicating-ios-crash-logs.html – ZeMoon Apr 22 '14 at 13:56
EXC_BAD_ACCESS usually means that you are sending a message to an object that no longer exists. – ZeMoon Apr 22 '14 at 13:59
i get .ips file in the crash report folder not .crash file do you have any idea about how to symobolicate it and also i have .ipa file and .dsym file – khaled Apr 23 '14 at 16:34
@akashg I know that sending messages to nil will not cause a crash. By the objective -c specification it is a perfectly valid thing to do. Sending it to nil is very different than sending it to an object that no longer exists. – David Berry Apr 26 '14 at 16:51

Unknown Crashes happened in SpriteKit

1 Answers1