Spritekit crashes when entering background
Asked Answered
H

2

11

Allright guys, I've been developing an app in which I have a NSMutableDictionary with an SKAction object in it. The SKAction is for playing a sound.

This all works well, except ... the app crashes upon entering background with the following stack trace:

* thread #1: tid = 0x187d7, 0x3461b932 libGPUSupportMercury.dylib`gpus_ReturnNotPermittedKillClient + 10, queue = 'com.apple.spritekit.renderQueue, stop reason = EXC_BAD_ACCESS (code=1, address=0x1)
frame #0: 0x3461b932 libGPUSupportMercury.dylib`gpus_ReturnNotPermittedKillClient + 10
frame #1: 0x3461c3d0 libGPUSupportMercury.dylib`gpusSubmitDataBuffers + 104
frame #2: 0x2eafc4a4 IMGSGX554GLDriver`SubmitPackets + 124
frame #3: 0x31f83cb0 GLEngine`gliPresentViewES + 168
frame #4: 0x31f8e136 OpenGLES`-[EAGLContext presentRenderbuffer:] + 62
frame #5: 0x002622e6 libglInterpose.dylib`EAGLContext_presentRenderbuffer(EAGLContext*, objc_selector*, unsigned int) + 370
frame #6: 0x323f9064 SpriteKit`-[SKView _renderContent] + 1220
frame #7: 0x3a90b0ae libdispatch.dylib`_dispatch_client_callout + 22
frame #8: 0x3a90f8f2 libdispatch.dylib`_dispatch_barrier_sync_f_invoke + 26
frame #9: 0x323f8b72 SpriteKit`-[SKView renderContent] + 82
frame #10: 0x323f651a SpriteKit`__29-[SKView setUpRenderCallback]_block_invoke + 130
frame #11: 0x32418c86 SpriteKit`-[SKDisplayLink _callbackForNextFrame:] + 254
frame #12: 0x002615fe libglInterpose.dylib`-[DYDisplayLinkInterposer forwardDisplayLinkCallback:] + 270
frame #13: 0x321d7ad2 QuartzCore`CA::Display::DisplayLinkItem::dispatch() + 98
frame #14: 0x321d787c QuartzCore`CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 344
frame #15: 0x34dd476c IOMobileFramebuffer`IOMobileFramebufferVsyncNotifyFunc + 104
frame #16: 0x30a5ebe4 IOKit`IODispatchCalloutFromCFMessage + 248
frame #17: 0x2fd3cb80 CoreFoundation`__CFMachPortPerform + 136
frame #18: 0x2fd47776 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
frame #19: 0x2fd47712 CoreFoundation`__CFRunLoopDoSource1 + 346
frame #20: 0x2fd45ede CoreFoundation`__CFRunLoopRun + 1406
frame #21: 0x2fcb0470 CoreFoundation`CFRunLoopRunSpecific + 524
frame #22: 0x2fcb0252 CoreFoundation`CFRunLoopRunInMode + 106
frame #23: 0x349b72ea GraphicsServices`GSEventRunModal + 138
frame #24: 0x32565844 UIKit`UIApplicationMain + 1136
frame #25: 0x000bd1bc SpritekitCrash`main(argc=1, argv=0x27d4dc5c) + 116 at main.m:16

Since it said EXC_BAD_ACCESS, I suspected zombie-objects, but enabling them in the scheme didn't help a thing in understanding this crash.

This even happens in the most minimalistic project setup (literally 2 lines of code) in MyScene.m:

self.arrSounds = [[NSMutableDictionary alloc] init];
[self.arrSounds setObject:[SKAction playSoundFileNamed:[NSString stringWithFormat:@"70.caf"] waitForCompletion:NO] forKey:[NSString stringWithFormat:@"1"]];

How is this possible?

You can download this project from my github page: https://github.com/SabatinoMasala/SpritekitCrash

Harmonize answered 26/11, 2013 at 22:44 Comment(1)
possible duplicate of Sprite Kit & playing sound leads to app terminationHartzell
H
13

Allright, I found the issue.

Behind the scenes, Spritekit uses AVAudioSession (which makes sense) for [SKAction playSoundFileNamed:]

AVAudioSession cannot be active while the application is in the background, so we have to stop it when going in to background, and reactivate it when entering foreground.

Use this piece of code in both applicationWillResignActive and applicationDidEnterBackground to disable the AVAudioSession:

[[AVAudioSession sharedInstance] setActive:NO error:nil];

To enable it again, use this in applicationWillEnterForeground:

[[AVAudioSession sharedInstance] setActive:YES error:nil];
Harmonize answered 27/11, 2013 at 10:0 Comment(2)
I have the same issue without any sounds. I'm pausing the SKScene view on background.Curettage
But your stacktrace says that it is OpenGL ("EAGLContext presentRenderbuffer"), so how could it be AVAudioSession ?Hamo
I
2

It's not enough, while setActive:NO often ends with error (no deactivation in effect) which still leads to the crash.

Full solution I've described here: Sprite Kit & playing sound leads to app termination

Inbreeding answered 25/1, 2014 at 11:35 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.