Help decoding a log file - App Crashes on Load

Question

I have an app written and it works perfectly, without error, in simulator and when running on a phone via xcode. Once I built my .xcarchive and signed to get the .ipa, I loaded onto the phone using Xcode / Devices Window.Then, when I click to open the app on the phone, it starts to open and then crashes.  😟an anyone help point me in a good direction to find my culprit?(FOR REFERENCE - Line 12 of my appdelegate is:                                   class AppDelegate: UIResponder, UIApplicationDelegate {Below is the log file from the phone:Incident Identifier: 85B2AD8C-683B-4486-860C-D1AEB532D825CrashReporter Key:   1b0a9b2a0c78297c6a8f3ac66d8af22b790ad094Hardware Model:      iPhone7,2Process:             Go To [281]Path:                /private/var/containers/Bundle/Application/2234A72A-A07B-42B4-95C4-13FF5B6D9872/go to.app/Go ToIdentifier:          com.****** REMOVED FOR COMPANY PRIVACY ******Version:             0 (2.0)Code Type:           ARM-64 (Native)Role:                ForegroundParent Process:      launchd [1]Coalition:           com.****** REMOVED FOR COMPANY PRIVACY ****** [433]Date/Time:           2018-05-22 12:18:16.1496 -0500Launch Time:         2018-05-22 12:18:15.9287 -0500OS Version:          iPhone OS 11.3.1 (15E302)Baseband Version:    6.55.00Report Version:      104Exception Type:  EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note:  EXC_CORPSE_NOTIFYTriggered by Thread:  0Application Specific Information:abort() calledFiltered syslog:None foundLast Exception Backtrace:0   CoreFoundation                 0x182ffed8c __exceptionPreprocess + 2281   libobjc.A.dylib               0x1821b85ec objc_exception_throw + 552   UIKit                         0x18d54d728 +[UIStoryboard storyboardWithName:bundle:] + 7833   UIKit                         0x18cfaffb8 -[UIApplication _loadMainStoryboardFileNamed:bundle:] + 914   UIKit                         0x18cbcd254 -[UIApplication _loadMainInterfaceFile] + 2755   UIKit                         0x18cb9b550 -[UIApplication _runWithMainScene:transitionContext:completion:] + 14116   UIKit                         0x18d1cba0c __111-[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:]_block_invoke + 7837   UIKit                         0x18cb9ae4c +[_UICanvas _enqueuePostSettingUpdateTransactionBlock:] + 1598   UIKit                         0x18cb9ace8 -[__UICanvasLifecycleMonitor_Compatability _scheduleFirstCommitForScene:transition:firstActivation:completion:] + 2399   UIKit                         0x18cb99b78 -[__UICanvasLifecycleMonitor_Compatability activateEventsOnly:withContext:completion:] + 72310  UIKit                         0x18d82f72c __82-[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:]_block_invoke + 29511  UIKit                         0x18cb99268 -[_UIApplicationCanvas _transitionLifecycleStateWithTransitionContext:completion:] + 43112  UIKit                         0x18d6149b8 __125-[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:]_block_invoke + 21913  UIKit                         0x18d762ae8 _performActionsWithDelayForTransitionContext + 11114  UIKit                         0x18cb98c88 -[_UICanvasLifecycleSettingsDiffAction performActionsForCanvas:withUpdatedScene:settingsDiff:fromSettings:transitionContext:] + 24715  UIKit                         0x18cb98624 -[_UICanvas scene:didUpdateWithDiff:transitionContext:completion:] + 36716  UIKit                         0x18cb9565c -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 53917  UIKit                         0x18cb953ac -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 36318  FrontBoardServices             0x1857fc470 -[FBSSceneImpl _didCreateWithTransitionContext:completion:] + 36319  FrontBoardServices             0x185804d6c __56-[FBSWorkspace client:handleCreateScene:withCompletion:]_block_invoke_2 + 22320  libdispatch.dylib             0x1828f0ae4 _dispatch_client_callout + 1521  libdispatch.dylib             0x1828f81f4 _dispatch_block_invoke_direct$VARIANT$mp + 22322  FrontBoardServices             0x185830878 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 3523  FrontBoardServices             0x18583051c -[FBSSerialQueue _performNext] + 40324  FrontBoardServices             0x185830ab8 -[FBSSerialQueue _performNextFromRunLoopSource] + 5525  CoreFoundation                 0x182fa7404 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 2326  CoreFoundation                 0x182fa6c2c __CFRunLoopDoSources0 + 27527  CoreFoundation                 0x182fa479c __CFRunLoopRun + 120328  CoreFoundation                 0x182ec4da8 CFRunLoopRunSpecific + 55129  GraphicsServices               0x184ea7020 GSEventRunModal + 9930  UIKit                         0x18cea578c UIApplicationMain + 23531  Go To                         0x1008a9fc4 main + 40900 (AppDelegate.swift:12)32  libdyld.dylib                 0x182955fc0 start + 3Thread 0 name:  Dispatch queue: com.apple.main-threadThread 0 Crashed:0   libsystem_kernel.dylib         0x0000000182a852ec __pthread_kill + 81   libsystem_pthread.dylib       0x0000000182c26288 pthread_kill$VARIANT$mp + 3762   libsystem_c.dylib             0x00000001829f3d0c abort + 1403   libc++abi.dylib               0x000000018218f2c8 __cxa_bad_cast + 04   libc++abi.dylib               0x000000018218f470 default_unexpected_handler+ 5232 () + 05   libobjc.A.dylib               0x00000001821b88d4 _objc_terminate+ 35028 () + 1246   libc++abi.dylib               0x00000001821a937c std::__terminate(void (*)+ 111484 ()) + 167   libc++abi.dylib               0x00000001821a9400 std::terminate+ 111616 () + 848   libdispatch.dylib             0x00000001828f0af8 _dispatch_client_callout + 369   libdispatch.dylib             0x00000001828f81f4 _dispatch_block_invoke_direct$VARIANT$mp + 22410  FrontBoardServices             0x0000000185830878 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 3611  FrontBoardServices             0x000000018583051c -[FBSSerialQueue _performNext] + 40412  FrontBoardServices             0x0000000185830ab8 -[FBSSerialQueue _performNextFromRunLoopSource] + 5613  CoreFoundation                 0x0000000182fa7404 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 2414  CoreFoundation                 0x0000000182fa6c2c __CFRunLoopDoSources0 + 27615  CoreFoundation                 0x0000000182fa479c __CFRunLoopRun + 120416  CoreFoundation                 0x0000000182ec4da8 CFRunLoopRunSpecific + 55217  GraphicsServices               0x0000000184ea7020 GSEventRunModal + 10018  UIKit                         0x000000018cea578c UIApplicationMain + 23619  Go To                         0x00000001008a9fc4 main + 40900 (AppDelegate.swift:12)20  libdyld.dylib                 0x0000000182955fc0 start + 4Thread 1:0   libsystem_pthread.dylib       0x0000000182c23b04 start_wqthread + 0Thread 2:0   libsystem_pthread.dylib       0x0000000182c23b04 start_wqthread + 0Thread 3:0   libsystem_pthread.dylib       0x0000000182c23b04 start_wqthread + 0Thread 4:0   libsystem_pthread.dylib       0x0000000182c23b04 start_wqthread + 0Thread 5 name:  com.apple.uikit.eventfetch-threadThread 5:0   libsystem_kernel.dylib         0x0000000182a63e08 mach_msg_trap + 81   libsystem_kernel.dylib         0x0000000182a63c80 mach_msg + 722   CoreFoundation                 0x0000000182fa6e40 __CFRunLoopServiceMachPort + 1963   CoreFoundation                 0x0000000182fa4908 __CFRunLoopRun + 15684   CoreFoundation                 0x0000000182ec4da8 CFRunLoopRunSpecific + 5525   Foundation                     0x0000000183939674 -[NSRunLoop+ 34420 (NSRunLoop) runMode:beforeDate:] + 3046   Foundation                     0x00000001839394dc -[NSRunLoop+ 34012 (NSRunLoop) runUntilDate:] + 847   UIKit                         0x000000018cb8a7e4 -[UIEventFetcher threadMain] + 1368   Foundation                     0x0000000183a49efc __NSThread__start__ + 10409   libsystem_pthread.dylib       0x0000000182c25220 _pthread_body + 27210  libsystem_pthread.dylib       0x0000000182c25110 _pthread_body + 011  libsystem_pthread.dylib       0x0000000182c23b10 thread_start + 4Thread 0 crashed with ARM Thread State (64-bit):    x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x000000010154ccf7    x4: 0x00000001821aeabd   x5: 0x000000016f55e4d0   x6: 0x000000000000006e   x7: 0xffffffffffffffec    x8: 0x0000000008000000   x9: 0x0000000004000000  x10: 0x0000000182c26110  x11: 0x0000000000000003   x12: 0xffffffffffffffff  x13: 0x0000000000000001  x14: 0x0000000000000000  x15: 0x0000000000000010   x16: 0x0000000000000148  x17: 0x0000000000000300  x18: 0x0000000000000000  x19: 0x0000000000000006   x20: 0x00000001b5202b40  x21: 0x000000016f55e4d0  x22: 0x0000000000000303  x23: 0x00000001b5202c20   x24: 0x0000000000000000  x25: 0x0000000000001d03  x26: 0x00000001b520f5e2  x27: 0x00000001b39bb964   x28: 0x000000010150c678   fp: 0x000000016f55e430   lr: 0x0000000182c26288    sp: 0x000000016f55e400   pc: 0x0000000182a852ec cpsr: 0x00000000

QuinceyMorris · Answer

&amp;gt;&amp;gt; Application Specific Information:&amp;gt;&amp;gt; abort() calledSince the application aborted itself deliberately, you can expect there will be a log message in the console. The backtrace suggests that the problem is in the loading of the initial storyboard.If it worked in the simulator and crashed on the device, I would guess that the problem is the case of letters in the storyboard name. (The iOS file system is case sensitive, while the macOS file system that the simulator uses is typically case insensitive.) That doesn&#x27;t seem to be the problem, if it works on the device when run from Xcode, but perhaps the problem is something of that general nature.

joelglofal · Answer

Other than pulling this log from the phone, what else can I use to help identify the issue?

QuinceyMorris · Answer

Hmm. You could try Debug -&amp;gt; Attach to Process by PID or Name and tell Xcode to wait for the process, then launch the app on the device. That might attach early enough to catch the exception.Given the place the exception occurred, it might be something to do with the storyboard. Can you try making another storyboard and setting it as the initial storyboard? It doesn&#x27;t have to have the right stuff in it, you just want to see if it can get as far as actually loading a storyboard, if it isn&#x27;t already. If the app gets as far as displaying the initial view, you could try putting in temp code to display alerts to see how much further it gets before throwing the exception.The other area to consider (where I don&#x27;t know enough to help) is whether the .ipa contains the correct architecture for the device. If it&#x27;s just bitcode, I don&#x27;t think the app will run without turning it into real executable code.

Help decoding a log file - App Crashes on Load

Replies