App Crash: Swift._assertionFailure

Hi!


Anybody can help me? I am developing app that creates local notification with actions (Yes/No) to call an API. It works well except

when I locked the phone or Turn off the display and terminate the app. BTW, I also terminates the app but I did not lock the phone or turn off display and it works pretty, only when I locked the phone I experienced this crash.


libswiftCore.dylibSwift._assertionFailure(_: Swift.StaticString, _: Swift.String, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never
TEST0x104f20000 + 2528216
TEST0x104f20000 + 2524528
libdispatch.dylib_dispatch_client_callout
libdispatch.dylib_dispatch_once_callout
libswiftCore.dylibswift_once
TEST0x104f20000 + 2523820
TEST0x104f20000 + 2523316
TEST0x104f20000 + 2522468
libdispatch.dylib_dispatch_client_callout
libdispatch.dylib_dispatch_once_callout
libswiftCore.dylibswift_once
TEST0x104f20000 + 2524512
TEST0x104f20000 + 6461756
TEST0x104f20000 + 6467644
UIKitCore-[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:]
UIKitCore-[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:]
UIKitCore-[UIApplication _runWithMainScene:transitionContext:completion:]
UIKitCore-[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:]
UIKitCore_UIScenePerformActionsWithLifecycleActionMask
UIKitCore-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]
UIKitCore-[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:]
UIKitCore-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]
UIKitCore-[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:]
UIKitCore-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]
UIKitCore+[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:]
UIKitCore_UISceneSettingsDiffActionPerformChangesWithTransitionContext
UIKitCore-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]
UIKitCore_UISceneSettingsDiffActionPerformActionsWithDelayForTransitionContext
UIKitCore-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]
UIKitCore-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]
UIKitCore-[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:]
UIKitCore-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]
UIKitCore-[UIApplication workspace:didCreateScene:withTransitionContext:completion:]
UIKitCore-[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:]
FrontBoardServices-[FBSSceneImpl _callOutQueue_agent_didCreateWithTransitionContext:completion:]
FrontBoardServices-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]
FrontBoardServices-[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:]
FrontBoardServices-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]
libdispatch.dylib_dispatch_client_callout
libdispatch.dylib_dispatch_block_invoke_direct$VARIANT$mp
FrontBoardServices__FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__
FrontBoardServices-[FBSSerialQueue _queue_performNextIfPossible]
FrontBoardServices-[FBSSerialQueue _performNextFromRunLoopSource]
CoreFoundation__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
CoreFoundation__CFRunLoopDoSource0
CoreFoundation__CFRunLoopDoSources0
CoreFoundation__CFRunLoopRun
CoreFoundationCFRunLoopRunSpecific
GraphicsServicesGSEventRunModal
UIKitCoreUIApplicationMain
TEST0x104f20000 + 6500312
libdyld.dylibstart

Replies

To make progress on this you need to:

  1. Crash a full crash report.

  2. Get it symbolicated.

For info on how to do this, see Acquiring Crash Reports and Diagnostic Logs and the related articles.

If you look at the backtrace you posted it’s clear that something in your app (line 2) is triggering a Swift assertion failure (line 1). Symbolicating your log will reveal the identity of the code in line 2, which should suggest a a path forward.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"